Issue metadata
Sign in to add a comment
|
Pri 0, Tabbing in latest canary to next control does not interrupt chromevox speech
Reported by
nimerjaber1@gmail.com,
Jan 16 2018
|
||||||||||||||||||||||||
Issue descriptionVersion: 65.0.3322.0 Reproduction Steps: 1. Enable Chromevox. 2. Alt+F to menu. 3. Up arrow a number of times. Observe that only one item is read out at a time, the reading of menu items is not interrupted as I press the up arrow multiple times. This also occurs on web pages, in dialog boxes, and in settings when tabbing through the interface. Strangely enough, navigating to next element with CVox commands does not seem to be effected. Expected: As a user presses a key, speech is interrupted, and the next item is uttered. Actual: This is not the case, and only one item is read out at a time.
,
Jan 17 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9678b7e8d2cddc1eded48b88a9a924a027148c54 commit 9678b7e8d2cddc1eded48b88a9a924a027148c54 Author: David Tseng <dtseng@chromium.org> Date: Wed Jan 17 19:00:40 2018 Fix queueing in Output module Partial revert/revision of https://chromium-review.googlesource.com/c/chromium/src/+/861189 Bug: 802305 TBR=dmazzoni@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I7731b845b7f71131aee344658c783834c510abb8 Reviewed-on: https://chromium-review.googlesource.com/869137 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#529832} [modify] https://crrev.com/9678b7e8d2cddc1eded48b88a9a924a027148c54/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js [modify] https://crrev.com/9678b7e8d2cddc1eded48b88a9a924a027148c54/chrome/browser/resources/chromeos/chromevox/cvox2/background/live_regions_test.extjs [modify] https://crrev.com/9678b7e8d2cddc1eded48b88a9a924a027148c54/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js
,
Jan 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/220fe67a3a73a1da41dba996e5d5ef328dfaa632 commit 220fe67a3a73a1da41dba996e5d5ef328dfaa632 Author: David Tseng <dtseng@chromium.org> Date: Thu Jan 18 00:19:57 2018 Do not trigger spoken feedback updates from message center Test: enable ChromeVox. Verify alerts are *not* spoken concerning ChromeVox being enabled. No need for that because ChromeVox already announces "ChromeVox (SpokenFeeedback) ready". Also, verify alerts *do* get spoken when plugging in a braille display. This is not a message center popup update, but a popup being created/shown. Bug: 802305 Change-Id: I497578097583bfc0e64d62b04fd65578820cc315 Reviewed-on: https://chromium-review.googlesource.com/871519 Reviewed-by: James Cook <jamescook@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#529971} [modify] https://crrev.com/220fe67a3a73a1da41dba996e5d5ef328dfaa632/ash/system/tray_accessibility.cc
,
Jan 18 2018
,
Jan 23 2018
Issue 804666 has been merged into this issue.
,
Feb 1 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dsexton@chromium.org
, Jan 16 2018Labels: -Pri-2 Pri-1
Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)