Closed Bug 1949713 Opened 1 year ago Closed 3 months ago

Firefox returns wrong AX Element positions on macOS on second monitors with high resolution

Categories

(Core :: Widget: Cocoa, defect, P3)

Product:
Core
Component:
Widget: Cocoa
Version:
Firefox 137
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1525379

People

(Reporter: guill.bout, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.3 Safari/605.1.15

Steps to reproduce:

ping Firefox AX UI Elements when using multiple monitors, with second monitor using a high resolution.

Actual results:

the AX UI Elements positions returned by Firefox is wrong. on single monitor they're right. on second monitor using a low resolution they are right too. but on second monitor using a high resolution, they are wrong.

Expected results:

Firefox should have returned the correct positions of the AX UI Elements even on second monitor with high resolutions.

attaching a video showing the issue.

video was too heavy for upload. attaching a public dropbox link here where you can view the issue: https://www.dropbox.com/scl/fi/3uovae6awk8v5lh2cyp5p/firefox-ax-issue.mp4?rlkey=aq8rhiwwa4hlgangvnu59ugr0&dl=0

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Cocoa
Product: Firefox → Core

+1 experiencing the same issue under the same circumstance

Severity: -- → S3
Priority: -- → P3

+1 also experiencing the same issue under these circumstances. Would appreciate attention as this has effects on my disability access software

+1 same issue under same circumstance.

+1 same issue under same circumstances

I don't fully grasp what's going on here but it seems possible that the fix for bug 1525379 will resolve this. The latest Nightly builds have that fix, can anyone reproduce this with the latest Nightly build?

(In reply to Josh Aas from comment #7)

I don't fully grasp what's going on here but it seems possible that the fix for bug 1525379 will resolve this. The latest Nightly builds have that fix, can anyone reproduce this with the latest Nightly build?

hey Josh! i can confirm that it works now. thank you!

Excellent!

Status: UNCONFIRMED → RESOLVED
Closed: 3 months ago
Duplicate of bug: 1525379
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.