WinForms (DpiUnawareGdiScaled): control renders in wrong location on scaled monitor

[ugumba]

This is in reference to #1700 which, with V105, corrected the size of WebView2 on a scaled monitor.
However, the offset in relation to the application window is still not correct.
(We have various legacy components which tie us to DpiUnawareGdiScaled for the time being.)

See screenshots below.
Only the rendered pixels are in the wrong location - mouse events behave as if the controls are positioned correctly. (I.e. I have to click a lot to the right and a bit down from what I see onscreen.)

Version
SDK: 1.0.1293.44
Runtime: Beta 105.0.1343.10
Framework: WinForms
OS: Win11

Repro Steps
Create a WinForms app, use DpiUnawareGdiScaled
Embed a WebView2 control at an offset within the main app Form (e.g. within a TabPage)
Launch, and move between unscaled/scaled monitors

Screenshots
On an unscaled monitor (the little gear button is the top left of the WebView2 content):

On a 150% scaled monitor with version 105 (notice that the position is incorrect):

On a 150% scaled monitor before version 105 (for reference only, notice that v105 corrects size, not position):

AB#48526450

[ugumba]

Duplicate of #2704.

[veevandyke]

Google discontinued support for maps in the old control as of yesterday, so this has now become mission critical to have it working. Any updates on this one?

[EnaXnaY]

Have same issue at 4K monitor ;) at normal notebook display and normal monitor (even if scaled) displayed correctly ;)

[tochukwuIbeEkeocha]

Known issue, adding to our backlog