Closed
Bug 1734582
Opened 3 years ago
Closed 3 years ago
Make TextLeafPoint handle display: contents
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
95 Branch
| Tracking | Status | |
|---|---|---|
| firefox95 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
Attachments
(1 file)
TextLeafPoint's line boundary code for LocalAccessibles depends on having a frame. Using display: contents means there'll be no frame. The code needs to be tweaked to handle that case. Right now, it throws an assertion.
I need to look at the existing behaviour here in the old HyperTextAccessible implementation, as well as what makes sense.
|
Assignee | |
Comment 1•3 years ago
|
||
This can happen for display: contents.
In that case, there are no lines in the Accessible anyway, so returning an invalid TextLeafPoint (as we already did) is the correct thing to do.
Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/570e6e45882f Don't assert for a null frame in TextLeafPoint::FindPrev/NextLineStartSameLocalAcc. r=morgan
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox95:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 95 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•