Issue metadata
Sign in to add a comment
|
Traversing cells quickly results in them not being read in SHeets with CVox Next
Reported by
nimerjaber1@gmail.com,
Aug 28 2016
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 55.0.2842.0 Reproduction Steps: 1. sheets.google.com 2. Open any document or create a new one. 3. down arrow three-four times at a medium speed, not even that fast, maybe 1 or 2x second.. Expected: *All* cells to be read out. Actual: About every other cell is not read. This occurs with Chromevox Next, with default Google TTS.
,
Aug 29 2016
,
Aug 29 2016
,
Sep 1 2016
Does this reproduce with Classic?
,
Sep 2 2016
No, Classic works fine.
,
Sep 9 2016
,
Sep 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/89cf7451ed3e6091f24c641309fe057f92817cf9 commit 89cf7451ed3e6091f24c641309fe057f92817cf9 Author: dtseng <dtseng@chromium.org> Date: Tue Sep 13 21:08:10 2016 Define a minimum delay time for processing live regions on the same node. This distinguishes the time we use to queue live region output vs the time we use to drop live regions if fired on the same ancestry. BUG= 641548 , 641548 , 641786 TEST=type rapidly in Docs; verify all key presses are echoed with braille mode off. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2332103003 Cr-Commit-Position: refs/heads/master@{#418369} [modify] https://crrev.com/89cf7451ed3e6091f24c641309fe057f92817cf9/chrome/browser/resources/chromeos/chromevox/cvox2/background/live_regions.js |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chaok@google.com
, Aug 28 2016