MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Control location coordinates incorrect when using UIAutomation and monitor scaling
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Description
Control location coordinates incorrect when using UI Automation, for multiple monitors where non Main Display > 100% scaled.
Version
SDK: Whichever MSEdgeWebView2 version is used in the new Teams and Outlook
Runtime: Whichever MSEdgeWebView2 version is used in the new Teams and Outlook
Framework: Whichever MSEdgeWebView2 version is used in the new Teams and Outlook
OS: Win10
Regression
Was this working before but has regressed? N/A
Repro Steps
2 Monitors (Main display) = 100% scaled. Monitor 2 = 125%.
Attempt to get the coordinates of a control (e.g. Chat button in new Teams which uses MSEDgeWebView2), using UIAutomation. Coordinates come back with an increased value for the Y coordinate. So, incorrect.
I hope this makes sense, and I'm not even sure if I'm posting this in the right place, but wanted to get the ball rolling somewhere.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.