Closed
Bug 1834874
Opened 1 year ago
Closed 1 year ago
Make Android text navigation use TextLeafPoint
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
116 Branch
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
(Whiteboard: [ctw-postship])
Attachments
(2 files)
The interface is much more akin to the TextLeafPoint API anyway. Might even be worth dropping the text API from Pivot altogether.
|
Assignee | |
Updated•1 year ago
|
Summary: Make Pivot text navigation use TextLeafPoint → Make Android text navigation use TextLeafPoint
|
|
Assignee | |
Comment 1•1 year ago
|
||
|
||
Updated•1 year ago
|
Assignee: nobody → eitan
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•1 year ago
|
||
Since we removed the last dependency on this subprotocol, we can now
remove it.
Depends on D181320
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8795b70dacdc
P1: Make text navigation work in UI thread with cached TextLeafPoint API. r=Jamie,geckoview-reviewers,m_kato
https://hg.mozilla.org/integration/autoland/rev/77adbef6592c
P2: Remove DocAccessiblePlatformExt. r=Jamie,ipc-reviewers,mccr8
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8795b70dacdc
https://hg.mozilla.org/mozilla-central/rev/77adbef6592c
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox116:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•