Adds an event handler for the AcceleratorKeyPressed event.
AcceleratorKeyPressed runs when an accelerator key or key combo is
pressed or released while the WebView is focused. A key is considered an
accelerator if either of the following conditions are true.
* Ctrl or Alt is currently being held.
* The pressed key does not map to a character.
A few specific keys are never considered accelerators, such as Shift.
The Escape key is always considered an accelerator.
Auto-repeated key events caused by holding the key down also triggers
this event. Filter out the auto-repeated key events by verifying the
KeyEventLParam or PhysicalKeyStatus event args.
In windowed mode, the event handler is run synchronously. Until you
run Handled() on the event args or the event handler returns, the
browser process is blocked and outgoing cross-process COM requests fail
with RPC_E_CANTCALLOUT_ININPUTSYNCCALL. All CoreWebView2 API methods
work, however.
In windowless mode, the event handler is run asynchronously. Further
input do not reach the browser until the event handler returns or
Handled() is run, but the browser process is not blocked, and outgoing
COM requests work normally.
It is recommended to run Handled(TRUE) as early as are able to know
that you want to handle the accelerator key.
Adds an event handler for the AcceleratorKeyPressed event. AcceleratorKeyPressed runs when an accelerator key or key combo is pressed or released while the WebView is focused. A key is considered an accelerator if either of the following conditions are true.
* Ctrl or Alt is currently being held. * The pressed key does not map to a character.
A few specific keys are never considered accelerators, such as Shift. The Escape key is always considered an accelerator.
Auto-repeated key events caused by holding the key down also triggers this event. Filter out the auto-repeated key events by verifying the KeyEventLParam or PhysicalKeyStatus event args.
In windowed mode, the event handler is run synchronously. Until you run Handled() on the event args or the event handler returns, the browser process is blocked and outgoing cross-process COM requests fail with RPC_E_CANTCALLOUT_ININPUTSYNCCALL. All CoreWebView2 API methods work, however.
In windowless mode, the event handler is run asynchronously. Further input do not reach the browser until the event handler returns or Handled() is run, but the browser process is not blocked, and outgoing COM requests work normally.
It is recommended to run Handled(TRUE) as early as are able to know that you want to handle the accelerator key.
\snippet ControlComponent.cpp AcceleratorKeyPressed