[Problem/Bug]: Is there a known problem with webview2 creating an Intermediate d3d window and intercepting mouse events?

[rcohn]

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

[rcohn]

Hello all - is there any chance that somebody on this WebView2 forum knows anything about this problem? Many thanks!

[yg-i]

I'm not completely sure but it sounds related to a problem I'm experiencing:

microsoft/terminal#15296 (comment)

[gplwzz1989]

I also encountered this issue. I used the --disable-gpu flag, but the intermediate D3D window still exists. When I use the --disable-gpu flag on my local Edge browser, it doesn't use the D3D window anymore. Is there any way to resolve this issue?