MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Left click spellcheck menu causes WebView to lost focus
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
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
- run the attached project and enter some incorrect spelling in the html page search box
- left click incorrect spelling
- select correct word from the menu
- the focus is set to the textbox control instead of WebView
Screenshots


Additional context
WindowsFormsApp1.zip
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached WindowsFormsApp1.zip project and reproduce the four listed steps using WebView2 SDK 1.0.1418.22 on WinForms. Inspect the WebView and textbox focus behavior after selecting a correction from the left-click spellcheck menu, and compare it with the right-click path. Done means a confirmed cause and a documented resolution or limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100