Closed
Bug 1696023
Opened 4 years ago
Closed 4 years ago
Position is incorrectly reported when calling Bounds() on a zero-area frame
Categories
(Core :: Disability Access APIs, defect, P3)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
88 Branch
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: morgan, Assigned: morgan)
Details
Attachments
(2 files)
STR: see attached mochitest
Neither screen readers nor the a11y inspector report bounds, so I had to test this in our mochitest framework
Assignee | ||
Comment 1•4 years ago
|
||
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
Comment 3•4 years ago
|
||
Backed out for causing failure at browser_zero_area.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/6c3a98d58bd335f127433324f26c08e013112754
Failure log: https://treeherder.mozilla.org/logviewer?job_id=332422332&repo=autoland&lineNumber=1753
Flags: needinfo?(mreschenberg)
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
Assignee | ||
Updated•4 years ago
|
Flags: needinfo?(mreschenberg)
Comment 5•4 years ago
|
||
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)
Assignee | ||
Comment 6•4 years ago
|
||
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
Comment 8•4 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
Updated•4 years ago
|
QA Whiteboard: [qa-88b-p2]
You need to log in
before you can comment on or make changes to this bug.
Description
•