In 1513447 there is a demonstrated instance in which the generated
marker is replaced with another one and throws the list item bullet
state into an unknown state. To remedy this we need to observe when such
elements are removed and added.
Instead of that, I opted to finally make the bullet accessible a real
content-backed accessible. This should help with other issues that pop
up when the list item overrides children management and keeps an
artificial accessible as its first child.
Differential Revision: https://phabricator.services.mozilla.com/D110719
This test checks accessibility properties of a non-native context menu and sends
synthetic keyboard events to it.
With native context menus, accessibility and keyboard interaction are handled
natively and cannot be tested, so this test can be disabled in that configuration.
Differential Revision: https://phabricator.services.mozilla.com/D112107
This test has a part where it expects AXMenuOpened events for context menus, which are not observable for us when native context menus are used.
It also has a part where it inspects the accessibility-exposed contents of a context menu. This is not testable with native context menus either, so that part of the test needs to be disabled.
Differential Revision: https://phabricator.services.mozilla.com/D112122
Previously, text children were excluded from the a11y tree, so they weren't considered when computing name from subtree.
Differential Revision: https://phabricator.services.mozilla.com/D111029
Previously, when determining the modifier, the code used the uncomposed document, which will be null for an element inside shadow DOM.
Differential Revision: https://phabricator.services.mozilla.com/D111033
Removes NPAPI plugin support from accessible/, as part of removing all of NPAPI plugin support. This was the only reason for HTMLWin32ObjectAccessible was needed, so we get rid of that, too.
Differential Revision: https://phabricator.services.mozilla.com/D107143
Removes NPAPI plugin support from accessible/, as part of removing all of NPAPI plugin support. This was the only reason for HTMLWin32ObjectAccessible was needed, so we get rid of that, too.
Differential Revision: https://phabricator.services.mozilla.com/D107143
Previously we relied on adding a visit to prompt the URL bar to autofill, that worked because nightly and release shipped with bookmarks to addons.moz. Beta, however, does not, so we should modify this test to populate the bookmark on all releases.
Differential Revision: https://phabricator.services.mozilla.com/D110571
Clicking at the top left previously worked, but doesn't work with browser.proton.enabled.
1. Support a { where: "center" } argument to synthClick in events.js.
2. Use that in the test.
Differential Revision: https://phabricator.services.mozilla.com/D109689
This fixes an inconsistency where CacheChildrenInSubtree uses the
flattened tree via DOM child iterators, but ProcessInvalidationList uses
GetContainerAccessible that doesn't currently use the flattened tree.
Differential Revision: https://phabricator.services.mozilla.com/D108980
We assumed parent content wasn't null because we've already checked that there is a parent table accessible, suggesting there's also parent content.
However, if the tr is at the top level of a shadow root (but the table is not), parent content will be null, causing a crash.
Before the fix for bug 1686123, this was fine because the frame for a shadow root is null and we didn't continue for a null frame.
Now that we do continue for a null frame, we must null check parent content.
Differential Revision: https://phabricator.services.mozilla.com/D108777
This commit adds an AXValue setter to incremental accessibles, as well
as tests to validate that setter on both a range and number input.
Differential Revision: https://phabricator.services.mozilla.com/D106333
I removed the functor and used a lambda instead.
To the tests, I added a "_mixed" case version of each role, to make sure they are all thoroughly tested.
Differential Revision: https://phabricator.services.mozilla.com/D108139
display: contents means there is no frame, which means we can't use HTMLTable*Accessible.
However, we can (and should) use ARIAGrid*Accessible in this case.
Differential Revision: https://phabricator.services.mozilla.com/D107407