MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Composition hosting — mouse and keyboard become unresponsive after repeatedly dragging outside the screen (regression: 151 OK, 152 broken)
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
Win32 composition hosting (ICoreWebView2CompositionController + SendMouseInput + host SetCapture/ReleaseCapture as in the official sample). Press and hold mouse inside WebView, drag cursor outside the screen, release; repeat several times. Eventually mouse and keyboard stop responding to WebView content until restart.
- Runtime 151.0.4129.x: not reproducible / very rare
- Runtime 152.0.4191.x: easy to reproduce with same host binary
Possibly related: #5687 (152 cursor regression), #5613 / #4772 / #5375 (input stuck after drag), #4968 (composition input stuck). Not claiming they are the same bug.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
Broken: 152.0.4191.53
Last working: 151.0.4129.x (fill exact)
SDK Version
(fill)
Framework
Win32
Operating System
Windows 11
OS Version
(fill, e.g. 10.0.26200)
Repro steps
- Use composition/visual hosting WebView (official API sample Visual mode preferred).
- LButton down inside WebView client.
- Drag cursor beyond monitor / virtual screen edge; release.
- Repeat 3–10 times.
- Observe clicks and keyboard no longer work on web content.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
151.0.4129.x
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.
Assessment
This issue has not been assessed yet.