Closed
Bug 1642707
Opened 6 years ago
Closed 6 years ago
Firefox no longer sends VoiceOver a notification that the page finished loading.
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
VERIFIED
FIXED
mozilla79
| Tracking | Status | |
|---|---|---|
| firefox-esr68 | --- | unaffected |
| firefox-esr78 | --- | wontfix |
| firefox77 | --- | wontfix |
| firefox78 | --- | wontfix |
| firefox79 | --- | verified |
People
(Reporter: MarcoZ, Assigned: morgan)
References
Details
(Keywords: regression, Whiteboard: [mac2020_1])
Attachments
(1 file)
This was implemented by Hub Figuiere in 2012 or 2013, but got broken some time ago, probably in E10S.
STR:
- In Safari, load any web site with VoiceOver on.
- Result: When the page finishes loading, VoiceOver emits three ascending tones that indicate that it is ready to read the page.
- Do the same in Firefox.
- Expected: We'd hear the same ascending tones.
- Actual: No tones are being played.
| Reporter | ||
Comment 1•6 years ago
|
||
I think this was broken even before Eitan's refactor in Bug 1624729. It was fired on the native accessible element. According to Chromium source, "AXLoadComplete" should only be fired on the root element, and "AXLayoutComplete" on iframes. We're firing all in both cases, and that might be wrong nowadays. Chromium changed that some time in 2015 or so.
NI'ing Eitan since we just talked about this on Zoom.
Flags: needinfo?(eitan)
Updated•6 years ago
|
Assignee: nobody → eitan
Flags: needinfo?(eitan)
| Assignee | ||
Updated•6 years ago
|
Assignee: eitan → mreschenberg
Updated•6 years ago
|
status-firefox77:
--- → wontfix
status-firefox78:
--- → wontfix
status-firefox-esr68:
--- → unaffected
status-firefox-esr78:
--- → affected
| Assignee | ||
Comment 2•6 years ago
|
||
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b03bb10f9e2e
Add web area class and attributes r=eeejay
Comment 4•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Confirmed lack of notification with 77.0b7.
Fix verified with 79.0b2 on macOS 10.5.5.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•