Map focusable state
- some Android apps require focusable nodes have either focus or makeVisible actions performed on them for some UI to show up (e.g. Assistant) - ChromeVox, as a result, needs to observe more containers. For focusable nodes, ChromeVox will not typically descend into their descendants unless the node's role is explicitly known to be a container. In Android, this is mostly nodes with role 'list'. their contents shown Navigate in other apps with many focusable containers e.g. Play Store. Verify navigation continues into descendants. Test: navigate in Assistant. Verify that invisible listItem nodes have Bug: 788650 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I3a6b512b3d133f6bae9e89dd11488229c0fe4660 Reviewed-on: https://chromium-review.googlesource.com/792098Reviewed-by:Yuki Awano <yawano@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#519813}
Showing
Please register or sign in to comment