New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 854867 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox: Moving selection up/down through rows quickly in hterm causes selection to be jumpy

Project Member Reported by raymes@chromium.org, Jun 21 2018

Issue description

For some reason selection becomes jumpy when moving it up/down quickly through rows. The orange highlighted region will appear to jump backward to a previous location.

To repro: 
1) Run hterm with latest accessiblity patches (I will provide another extension which you can load with the latest patches)
2) Press ChromeVox+Up and see that the previous rows of output get highlighted.
3) Hold down ChromeVox+Up and it jumpily navigates through previous rows 
 

Comment 1 by raymes@chromium.org, Jun 21 2018

Labels: OS-Chrome

Comment 2 by dtseng@chromium.org, Jun 26 2018

I don't see this. Could you try to come up with a minimal snippet?
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 29 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2622f055d69674e682cd1a466912df69d6774bdd

commit 2622f055d69674e682cd1a466912df69d6774bdd
Author: David Tseng <dtseng@chromium.org>
Date: Fri Jun 29 18:44:29 2018

Ignore document selection changes triggered by actions

Bug:  854867 
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I69de2def818e7e91f5cb7e4a3ff1051a517101c1
Reviewed-on: https://chromium-review.googlesource.com/1117459
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#571567}
[modify] https://crrev.com/2622f055d69674e682cd1a466912df69d6774bdd/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js

Comment 4 by dtseng@chromium.org, Jun 29 2018

Status: fixed (was: Assigned)

Sign in to add a comment