[jdk18] RFR: 8279227: Access Bridge: Wrong frame position and hit test result on HiDPI display [v2]

[Sergey Bylokhov]

On Mon, 27 Dec 2021 15:08:34 GMT, Anton Tarasov <ant at openjdk.org> wrote:

> I've checked it - it does not change, which is unexpected... Doesn't it seem like a bug?

Yes, I think this is a bug.

> Actually, the problem is that AccessibleComponent does not provide the component's GC, which is a missing. Ideally would be to add it to the API and then use - because it already contains actual scales for the component. It's a pity to do all that calculations just because we lack API calls...

But do we actually need the GC where the component is located, or do we need a GC where the a11y frame should be placed? I am not sure that both are always the same. Note that you can find the screen where the "virtual coordinates are located" and then convert them to the device space.

-------------

PR: https://git.openjdk.java.net/jdk18/pull/72