Fire ACTIVE state change events
Categories
(Core :: Disability Access APIs, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
(Regressed 1 open bug)
Details
Attachments
(5 files)
I don't think we care about the root accessible case since that shouldn't happen in remote content.
We do care about aria-activedescendant
though..
Assignee | ||
Comment 1•3 years ago
|
||
Changing severity to S3 because this is ongoing cache the world work that does not affect current users.
Assignee | ||
Comment 2•3 years ago
|
||
We do this in a bunch of places, so I moved it into promisified-events.
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
By allowing async DOM events to be dispatched, and advancing the refresh
driver we can force some calls to NotificationController::WillRefresh
and flush out any pending notifications or events.
This lets us more reliably catch unexpected events without the need for
a sentinel event at the end.
Depends on D130294
Assignee | ||
Comment 4•3 years ago
|
||
Have ARIAActiveDescendantIDMaybeMoved call ARIAActiveDescendantChanged regardless of
widget focus state. The latter already checks if the widget is focused. This gives us
a chance to fire and ACTIVE state change regardless of focus state.
If an id or aria-activedescendant attribute is about to change, fire an
ACTIVE state change on the previously active accessible.
Depends on D130295
Assignee | ||
Comment 5•3 years ago
|
||
This will make it easier to work with in a later change.
Depends on D130296
Assignee | ||
Comment 6•3 years ago
|
||
- Use dom events in RootAccessible to fire ACTIVE state changes.
- Add DOMMenuItemInactive events to nsListControlFrame and fire it on
the previously active option. - Don't fire those DOM events on collapsed combo boxes.
- Add ACTIVE state change events for collapsed combo box options.
Depends on D130297
Comment 9•3 years ago
|
||
Backed for causing leakes.
Backout link: https://hg.mozilla.org/integration/autoland/rev/fb93690f7303b09fc8ae2f94e65c3fa3f6a10f39
Failure log: https://treeherder.mozilla.org/logviewer?job_id=357578696&repo=autoland&lineNumber=2577
Assignee | ||
Comment 10•3 years ago
|
||
I just rebased on central, tried to reproduce this locally and in try, and that specific task passes with no problem:
https://treeherder.mozilla.org/jobs?repo=try&revision=847c983bc6d4a93cb7257ef4c82f22b59b06a67c&selectedTaskRun=cRKD2kBaTKSnRtVwbiu-5A.0
I can't think of anything in the patch that would cause a JSRuntime leak.
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f6ea433343d6
https://hg.mozilla.org/mozilla-central/rev/d501ebf13af2
https://hg.mozilla.org/mozilla-central/rev/d6b82d560ad6
https://hg.mozilla.org/mozilla-central/rev/edcc0183f30d
https://hg.mozilla.org/mozilla-central/rev/1685016c0c79
Updated•3 years ago
|
Description
•