Issue metadata
Sign in to add a comment
|
Chrome vox reads Search and content of text when typing into Google Search Box
Reported by
nimerjaber1@gmail.com,
Jun 18 2016
|
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 53.0.2768.0 Reproduction Steps: 1. Enable Chromevox Next 2. Navigate to www.google.com and type memristor in the search box. Expected Result: Chromevox honors the speak typed characters or words setting and does not speak extraneous information. Actual Result: Chromevox speaks search and the content of what has been typed after each letter press. For example, search M Search MEC Search MEM...
,
Oct 3 2016
This is still the case in 55.0.2878.0
,
Oct 3 2016
,
Oct 4 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5d1bf66ecc361012770c73136a5bb22a6a22176f commit 5d1bf66ecc361012770c73136a5bb22a6a22176f Author: dtseng <dtseng@chromium.org> Date: Tue Oct 04 00:06:43 2016 Don't read aria attribute changes on editables. By typing into an editable, aria attributes do often change (e.g. aria label). Read the attributes on demand (e.g. when a user navigates back to the control or requests a summary of the current element). CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation BUG= 621324 Review-Url: https://codereview.chromium.org/2389793002 Cr-Commit-Position: refs/heads/master@{#422612} [modify] https://crrev.com/5d1bf66ecc361012770c73136a5bb22a6a22176f/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
,
Oct 6 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lpalmaro@chromium.org
, Jun 20 2016Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)