Closed
Bug 1956150
Opened 10 months ago
Closed 10 months ago
Fire UIA AsyncContentLoaded event
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
138 Branch
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
We should fire UIA AsyncContentLoaded for EVENT_DOCUMENT_LOAD_COMPLETE. This alone doesn't seem to be enough to get Narrator to auto read the document (bug 1949921), but this Chromium commit suggests that this is at least part of the equation:
This change fires UIA_AsyncContentLoaded as the UIA analogue to IA2_EVENT_DOCUMENT_LOAD_COMPLETE. Narrator plans to use this to determine when to start auto-reading webpages.
We should support this event anyway, so let's get this landed here and add deal with other fixes separately.
|
Assignee | |
Comment 1•10 months ago
|
||
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9f9ce883cf0b
Fire the UIA AsyncContentLoaded event. r=morgan
|
||
Comment 3•10 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox138:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•