MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Is there a known problem with webview2 creating an Intermediate d3d window and intercepting mouse events?
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
Hello -
We have a WinUI 3 application that has incorporated webview2 support. Recently, we discovered that after the system powers up (either Win 10 or Win 11), and our app automatically starts, half of the display upon which the app starts up is not receptive to mouse events (selection, clicks). Using spy++, we discovered that an Intermediate d3d Window is running on the half of the screen blocking the mouse events. When the app is closed, mouse selection returns to normal. If the app is restarted (without doing a power cycle), then that also allows normal mouse events.
I discovered that by disabling display acceleration from System > Display > Graphics > Default graphics settings, I no longer see this behavior.
Is there a known problem with webview2 and Intermediate D3D Window causing such behavior?
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
Microsoft Edge WebView2 Runtime 126.0.2592.68
SDK Version
Windows App SDK 1.3.230502000
Framework
WinUI3/WinAppSDK
Operating System
Windows 10, Windows 11
OS Version
No response
Repro steps
Start up system
Upon user login, the app starts up automatically
Use the mouse to try and select/click on desktop icons on left side of display
Those icons and not selectable
Mouse can also not marquee on that side
The right side of the display processes mouse events normally
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Don't know
Last working version (if regression)
No response
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
No repository files, tests, or code entry points are named. Start by following the login-startup repro with the WinUI 3 app and WebView2 Runtime 126.0.2592.68, using Spy++ to inspect the Intermediate D3D Window and comparing display acceleration enabled versus disabled. Done means identifying a reproducible cause and a validated resolution for the intercepted mouse events.
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
- Needs clarification
- Newbie friendliness
- 25/100