Nic Champagne Williamson [MSFT]

Glad you got it working! I've opened this as a bug on our backlog to track making sure we fix this in the future.

Hey @ItsCubeTime - Yes this is still being tracked, but is lower priority for us. May I ask what your scenario is that you need this feature? It's possible we...

Hey @ItsCubeTime - Thanks for the info and scenario link. I believe this is generally possible if using the WebView2 Win32 control and changing the attributes of/clipping the HWND parent,...

Thanks for the bug report @ZbynekImmersive - sorry you are running into this. I've added it as a bug on our backlog. You mentioned that this happens on "certain websites"....

Thanks for the bug report @RickStrahl! I've added this to our backlog.

Thanks for the ping Rick. @yildirimcagri do you have any info on this issue?

@clshan-13 Those mouse events are WPF, so aren't available in Win32. For mouse events in Win32 you need to handle messages sent to your HWND. For an example of this,...

Thanks for checking #112. I'm tracking this on our backlog separately. Anything we build for our core Win32 control will also be projected in some way for our .NET controls,...

If your main use-case are accelerator keys, then we've exposed the [ICoreWebView2::add_AcceleratorKeyPressed](https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2controller?view=webview2-1.0.664.37#add_acceleratorkeypressed) in the regular WPF KeyDown event of the WPF WebView2 control. It doesn't capture every keypress though. The...

Sorry if my comment above wasn't clear. We are raising the corresponding KeyDown events for accelerators, so you should be able to do the following: ```cs private void webView_KeyDown(object sender,...