Closed Bug 1696023 Opened 3 years ago Closed 3 years ago

Position is incorrectly reported when calling Bounds() on a zero-area frame

Categories

(Core :: Disability Access APIs, defect, P3)

defect

Tracking

()

RESOLVED FIXED
88 Branch
Tracking Status
firefox88 --- fixed

People

(Reporter: morgan, Assigned: morgan)

Details

Attachments

(2 files)

Attached file browser_zero_area.js

STR: see attached mochitest
Neither screen readers nor the a11y inspector report bounds, so I had to test this in our mochitest framework

Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/318e51f44e8b
Report accessible's position even when bounds rect is empty r=Jamie
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1ab658549265
Report accessible's position even when bounds rect is empty r=Jamie
Flags: needinfo?(mreschenberg)

Backed out 2 changesets (bug 1695716, bug 1696023) for causing bc failures in browser_zero_area.js
Backout link: https://hg.mozilla.org/integration/autoland/rev/545cbce0417543215b3347a006c226092ba61361
Push with failures, failure log.

Flags: needinfo?(mreschenberg)
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b317b788a83b
Report accessible's position even when bounds rect is empty r=Jamie
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
QA Whiteboard: [qa-88b-p2]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: