Closed
Bug 1668961
Opened 4 years ago
Closed 4 years ago
Move state check in get string for range to content side
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
RESOLVED
FIXED
83 Branch
| Tracking | Status | |
|---|---|---|
| firefox83 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
Details
(Whiteboard: [mac2020_2])
Attachments
(1 file)
We right now do 2 sync round trips for getting the string range. We should just have to do one and check the state in the content side.
|
Assignee | |
Comment 1•4 years ago
|
||
The state checking can happen in the iterator in HyperTextAccessibleWrap.
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f8d86e937a0b
Avoid 2 IPC round trips in moxStringForTextMarkerRange. r=morgan
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox83:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 83 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•