WebView2 applications default to wrong capture mode

[ToadLobe]

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

32.1.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/v35OJbvTxVo8npty

OBS Studio Crash Log URL

No response

Expected Behavior

When running games based on WebView2:

• The "Automatic" capture method should use Windows 10 rather than BitBlt. It currently defaults to BitBlt, which is not compatible with Chromium based applications.
• Users should be shown the same warning that Chromium-based windows often trigger, i.e. Applications based on Chromium may not be capturable using the selected Capture Method (BitBlt). A similar message usually appears in both game capture and window capture modes.

Current Behavior

When running games based on WebView2:

• The "Automatic" capture method defaults to BitBlt and does not work (shows a white screen).
• No warning is shown to the user in game capture or window capture modes.

Steps to Reproduce

1. Launch an app based on WebView2
2. Attempt to capture the window with game capture or window capture

Here is an example application: Test.zip

Anything else we should know?

Developers of WebView based games (the Construct 3 engine uses WebView, as do Tauri applications) want to reduce friction for streamers wherever possible, and users unfamiliar with how OBS works may struggle to capture such games.

I am completely unfamiliar with the OBS codebase and am hoping someone could point me in the right direction - I only make this request because OBS does such a good job of identifying and warning users when the application is Chromium based (e.g. NWjs, Electron, CEF all detected), I wondered if a similar could be used to detect WebView based games (which are ultimately Chromium too). Thanks in advance!