Issue metadata
Sign in to add a comment
|
ChromeVox touch: focus cycling through entire paragraph while reading by line |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 69.0.3494.0 (Official Build) dev (64-bit), Firmware Version Google_Eve. 9584.160.0 Steps to reproduce: # Flip convertible ChromeVox into tablet mode # Turn on ChromeVox by holding both hardware volume keys for 5 seconds # Load a page with text such as https://en.wikipedia.org/wiki/Platypus # Start to use linear navigation gesture to hear text read (one finger left/right swipe) or use line-by-line gesture (one finger swipe up or down) Expected: as you move line to line, focus follows one line at a time, one line is read Actual: focus moves quickly in a cycle around a specific paragraph before landing back where focus should be, some words are spoken during this time
,
Aug 1
,
Aug 7
,
Aug 9
This bug needs a narrower reproduction such as the specific piece of html that triggers this behavior.
,
Oct 4
,
Oct 4
,
Oct 8
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/04639cbc23862a8085a75b310dc12669dab0d3d2 commit 04639cbc23862a8085a75b310dc12669dab0d3d2 Author: David Tseng <dtseng@chromium.org> Date: Mon Oct 08 14:55:41 2018 Use tree path based recovery by default Currently, ChromeVox recovers to ancestors when nodes are deleted from the accessibility tree. This often times does not do exactly what we want. For example, when a page quickly removes and re-inserts a the same or similar node, ChromeVox loses its place. This also can lead to ChromeVox getting "stuck" in a navigational loop. Tree path based recovery is already used within editable text, so has good coverage. TreePathRecoveryStrategy (the class) is also a subclass of AncestorRecoveryStrategy, so it falls back to ancestry-based recovery when the tree path is invalid. An alternate approach was tried in: https://chromium-review.googlesource.com/c/chromium/src/+/1234856 Test: the new Google.com accessibility menu now does not loop when navigating with ChromeVox. Bug: 869914,885244 Change-Id: I129e2b31250c2f3169feb662b042e6900f61e424 Reviewed-on: https://chromium-review.googlesource.com/c/1262435 Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#597562} [modify] https://crrev.com/04639cbc23862a8085a75b310dc12669dab0d3d2/chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs [modify] https://crrev.com/04639cbc23862a8085a75b310dc12669dab0d3d2/chrome/browser/resources/chromeos/chromevox/cvox2/background/cursors.js
,
Jan 11
This issue has been marked as started, but has no owner. Making available. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Aug 1