зеркало из https://github.com/mozilla/gecko-dev.git
ba3c5e3b7b
If we send an Android ACCESSIBILITY_FOCUSED event because of a content update (ie. scrolling to anchor or DOM selection changes) we should not scroll the accessible into view. We should assume the content is being brought into view by itself. Testing: We already have tests to show that we scroll an accessible into view when navigating content, testing for the inverse (that the scroll is done by other means and NOT a11y) is very hard. Differential Revision: https://phabricator.services.mozilla.com/D199433 |
||
|---|---|---|
| .. | ||
| AccessibleWrap.cpp | ||
| AccessibleWrap.h | ||
| ApplicationAccessibleWrap.h | ||
| DocAccessibleWrap.cpp | ||
| DocAccessibleWrap.h | ||
| Platform.cpp | ||
| RootAccessibleWrap.h | ||
| SessionAccessibility.cpp | ||
| SessionAccessibility.h | ||
| TraversalRule.cpp | ||
| TraversalRule.h | ||
| moz.build | ||