[Problem/Bug]: Gamepad input stops working when Steam Overlay is enabled in WebView2 apps

What happened?

Description
When using Microsoft WebView2 for Windows applications, gamepad input stops
working if Steam Overlay is enabled.

If Steam Overlay is disabled, gamepad input works again, but Steam features
are lost.

This affects games exported with Construct 3 and likely other WebView2-based apps.

Steps to reproduce

1. Export a Windows app using WebView2 (Construct 3)
2. Add the app to Steam
3. Enable Steam Overlay
4. Launch the app via Steam
5. Connect a gamepad (Xbox or compatible)

Expected:
Gamepad input works normally.

Actual:
Gamepad input does not work when Steam Overlay is enabled.

Expected behavior
Gamepad input should work even when Steam Overlay is enabled.

Actual behavior
Gamepad input only works when Steam Overlay is disabled.

Additional context
Scirra (Construct 3 developers) confirmed this is a WebView2 limitation.
This issue impacts multiple indie developers releasing games on Steam.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

Latest Stable WebView2 Runtime

SDK Version

N/A (used via Construct 3 export)

Framework

Win32

Operating System

Windows 10, Windows 11

OS Version

Windows 10 / Windows 11 (latest updates)

Repro steps

1. Export a Windows app using WebView2 (e.g., Construct 3 exported game)
2. Add the exported app to Steam
3. Enable Steam Overlay
4. Launch the app via Steam
5. Connect and use a gamepad

Expected: Gamepad input should work even when Steam Overlay is enabled.
Actual: Gamepad input does not work when Steam Overlay is enabled.

Expected:
Gamepad input works normally.

Actual:
Gamepad input does not work unless Steam Overlay is disabled.

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