-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Left click spellcheck menu causes WebView to lost focus #3012
Comments
Hi @kwystemp, This version of spellcheck has been disabled in WebView2 and is reverted to the old spellcheck feature. Can you check if you are still getting this issue? Thanks |
Hi @nishitha-burman, |
Hi @kwystemp are you used an Evergreen or Fixed version of WebView2? And what version of the runtime are you using? |
Hi @nishitha-burman, I used Evergreen bootstrapper and have 107.0.1418.62 runtime version installed. |
Are you still facing this issue? |
Description
Hi,
I'm using the WebView2 control to render html page inside outlook plugin I implement. I've found that if I try to correct some spelling issue on the page using left mouse click context menu, the plugin loses focus after correct spelling is selected from the menu.
I've recreated the problem in simplified project containing only WebView and textbox control - after correct spelling is selected, focus moves to the textbox control instead staying on the WebView - please see attached project.
Using the right click also brings the spell checking menu and it works fine in simplified scenario, but unfortunately I can't use this option in my project as I have a CkEditor4 control on my html page that overrides default right click menu.
SDK: 1.0.1418.22
Framework: WinForms
OS: Windows 10 Enterprise
Repro Steps
Screenshots
![image](https://user-images.githubusercontent.com/5364431/205102047-f604ec58-668c-4598-9989-053064beadcd.png)
![image](https://user-images.githubusercontent.com/5364431/205102451-1cf9e858-ef35-4520-bc60-5457620ba59c.png)
Additional context
WindowsFormsApp1.zip
The text was updated successfully, but these errors were encountered: