зеркало из https://github.com/mozilla/gecko-dev.git
9d9377be5e
We already handled this for visible aria-labelledby/describedby subtrees based on a11y events. However, when a subtree is hidden (whether via CSS or aria-hidden), it is completely removed from the a11y tree, so we can't use a11y events. Instead, when a node is added to the DOM, we walk its ancestors looking for an aria-labelledby/describedby target. We stop if the node or an ancestor has an Accessible, since that means it will be handled elsewhere. This also limits the number of ancestors we walk for each inserted node, thus decreasing the performance impact of this change. This doesn't catch all possible mutations in a hidden subtree (e.g. removals or direct text node changes), but this at least fixes a case in Gmail. Given performance risks, I think it makes sense to address specific cases as they arise. Differential Revision: https://phabricator.services.mozilla.com/D147559 |
||
|---|---|---|
| .. | ||
| browser | ||
| crashtests | ||
| mochitest | ||