Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UIA isn't properly handling display scale value #807

Closed
dayman40 opened this issue May 6, 2021 · 5 comments
Closed

UIA isn't properly handling display scale value #807

dayman40 opened this issue May 6, 2021 · 5 comments
Labels
bug Something isn't working
Milestone

Comments

@dayman40
Copy link
Contributor

dayman40 commented May 6, 2021

Here are two issues that I found with UIA mixing and matching physical and logical pixels:

In CUIAWindow::ElementProviderFromPointImpl, physical screen pixels are passed in, and we then convert those to physical app pixels, but then we pass those physical pixels into our hit-testing stack without converting them to logical pixels. Converting to logical pixels fixes this issue.
In CUIElement::TransformToWorldSpace, we account for the scale in the case where we've found the root visual in UWP apps, but we've already accounted for the scale at that point, meaning that we've multiplied by the scale twice. Here, we just don't need to account for the scale.

@ghost ghost added the needs-triage label May 6, 2021
@andrewleader andrewleader added bug Something isn't working and removed needs-triage labels May 12, 2021
@andrewleader andrewleader added this to the 0.5 (2021 Q1) milestone May 12, 2021
@riverar
Copy link
Contributor

riverar commented May 13, 2021

@andrewleader Is the milestone correct here?

@andrewleader
Copy link
Contributor

Yes, we're aiming at fixing this in a 0.5 servicing update (we've currently just been using 0.5 as the milestone including servicing fixes, if you think we should create separate milestones for each servicing update let us know!)

@riverar
Copy link
Contributor

riverar commented May 13, 2021

@andrewleader Oh got it. Might be less confusing if the milestone name reflected the actual update version (e.g. 0.5.9). And maybe not have "Q1" designation (which has passed).

@andrewleader
Copy link
Contributor

Yeah agreed. We'll try to improve that in the future by looking at what other GitHub repos do and see if there's a best practice. Just for transparency, I don't think we're going to address figuring that out soon (got lots of other higher impact topics to focus on).

@btueffers
Copy link
Contributor

Fixed in 0.5.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants