Wrong coordinates on the multiple monitors setup

[rootaman]

I have 3 monitors...

1. 3840 x 2160 @ 150% placed at the Top-Left with no rotation
2. 1920 x 1080 @ 125% placed at the Bottom-Left with no rotation
3. 1920 x 1080 @ 100% placed at the Middle-Right, this one rotate 90 degree (portrait)

UIViewer.ahk reports correct x,y or BoundingRectangle nicely only on the monitor 1 & 2
I always got wrong x,y or BoundingRectangle on the monitor 3, any hilight of the capturing element under my mouse cursor did not show correctly too (the hilights are mostly showed on monitor 2 even ALL the element was from the monitor 3)

[Descolada]

I don't have access to a three-monitor setup, but on a dual-screen one the issue is mostly fixed by adding the line DllCall("SetThreadDpiAwarenessContext", "ptr", -3, "ptr") to the top of UIAViewer.ahk. This sets the DPI awareness of the script to "per-monitor", which causes UIA to properly adjust for DPI across monitors. In fact, I'm a bit surprised at the inconsistent behavior of UIA in this, mainly that it worked in monitors 1&2 at all. For example, Notepad is per-monitor aware but UIAViewer works properly in it without the SetThreadDpiAwarenessContext, yet Word which is also per-monitor aware does not report correct coordinates.

The issue remains mostly with Chromium-based windows, where coordinates are still reported wrong. I guess this is an application-based issue and could probably be adjusted for in a per-application basis, but I don't know a general solution. Accessibility Insights gets reported wrong coordinates as well, so it's not just UIAViewer.

[rootaman]

Additional result from my test...I have test with 2 monitors now

1st display is 4K resolution, 2nd display is 1080p resolution... tried with different dpi settings for both of them.

1. The wrong coordinates happen only when working with Chrome (UIA_Browser) and within every child elements in the Doc. The Chrome's UI like tabs or icons on the toolbar are fine, also main Document element is correctly shown its coordinates too.
2. The wrong coordinates happen only when I test on the 2nd "Extended" display which is arranged "below" the 1st "Main" display regardless of their dpi settings , I have not try the "Left-Right" arrangement since my physical monitors arranged vertically...
3. If I arrange the main display below the 2nd extended display then all coordinates report correctly.

It looks like the UIA_Browser shift-away every Chrome document's child elements by some amount of pixels... when the Chrome window is placed on the extended display AND that display is positioned below the Main display ( AND when both displays have different resolutions? ).

[Descolada]

UIA_Browser doesn't shift anything. This is a bug on part of Microsoft and I reported it back in September, and it turns out they've known about it for a while already. There is a fix in the pipelines so hopefully we'll see results in a few months.

[rootaman]

Thanks for clarify the problem now it depends on Microsoft then...