[Problem/Bug]: Touch keyboard appears on wrong monitor for password input fields after WebView2 version update

What happened?

When a user taps on a password input field in WebView2, the Windows touch keyboard appears on the wrong monitor (a secondary display) instead of the monitor where the WebView2 host window is located.
This issue was introduced in a recent WebView2 version update. The same application code works correctly with older WebView2 versions.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

142.0.3595.80

SDK Version

No response

Framework

Win32

Operating System

Windows 11

OS Version

26100.7462

Repro steps

1. Set up a multi-monitor configuration (e.g., primary monitor at 0,0 and secondary monitor at 2560,0)
2. Host a WebView2 control in a native Win32 application on the primary monitor
3. Open Microsoft Edge browser (or any other app with an input field) on the secondary monitor
4. Click/tap on an input field in the Edge browser on the secondary monitor to give it focus (this makes the secondary monitor the "last active input location")
5. Now switch to the WebView2 host application on the primary monitor
6. Tap the password input field in WebView2 to trigger the Windows touch keyboard
7. Expected: Touch keyboard appears on the primary monitor (same as the WebView2 window)
8. Actual: Touch keyboard appears on the secondary monitor (where the Edge browser was focused earlier)

Repros in Edge Browser

Not test for now

Regression

Regression in newer Runtime

Last working version (if regression)

137.0.3296.93

AB#60735746