Issue metadata
Sign in to add a comment
|
Accessible mode not automatically triggered in Google Sheets
Reported by
ni...@jaberspace.com,
Oct 18 2016
|
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 56.0.2894.0 Reproduction Steps: 1. sheets.google.com 2. New Sheet with blank template 3. navigate around a document Expected: Accessible mode would be triggered if Chromevox Next is running. Actual: This does not happen. This is the cause of the last few bug reports that I reported... restarting Chromevox while Sheets is running fixed my problems.
,
Oct 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1f44b4e2c4b84f0111028ef02b4006f1d8afb079 commit 1f44b4e2c4b84f0111028ef02b4006f1d8afb079 Author: dtseng <dtseng@chromium.org> Date: Tue Oct 25 18:34:57 2016 Fix next compat to convey state for classic. ChromeVox's content script requests a boolean isClasicEnabled before document load (sometimes). Ensure that boolean accounts for the next compat reg exp. BUG= 657098 , 657100 , 657092 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2443273002 Cr-Commit-Position: refs/heads/master@{#427420} [modify] https://crrev.com/1f44b4e2c4b84f0111028ef02b4006f1d8afb079/chrome/browser/resources/chromeos/chromevox/cvox2/background/background.js |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Oct 24 2016