Issue metadata
Sign in to add a comment
|
ARC++: AccessibilityNodeInfo tree ordering does not match visual layout |
||||||||||||||||||||||||
Issue descriptionaccessibility services on Android perform some amount of reordering of the accessibility tree as follows (code within utils): - for a given node N, - if N is either not visible or is focusable, consider its children ordered - otherwise, use the children of N to compute ordering The ordering is top to bottom, left to right. Currently, in ARC++, we do not do the right thing. For example, in Play Store, the app drawer (e.g. the navigation menu button) appears at the end of navigation.
,
Feb 28 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Feb 26 2018