Issue metadata
Sign in to add a comment
|
ChromeVox Next Superfluously vocalizing input name for every letter typed into it |
||||||||||||||||||||
Issue descriptionChrome Version: 61.0.3163.123 OS: ChromeOS What steps will reproduce the problem? (1) On a ChromeOS device, go to classroom.google.com (2) Create a class (+ icon in the top right > Create class) (3) In the "Topics" left sidebar, click on the "Add Topic" button. (4) Type a letter into the input box, listen to ChromeVox Next vocalization. Repeat. What is the expected result? Typing a letter into the input should only vocalize the letter typed. What happens instead? Every time a letter is typed, ChromeVox Next vocalizes "Topic <letter typed> Edit text" Note: This works fine when I use the ChromeVox extension, it's only broken on ChromeVox Next.
,
Dec 13 2017
Should be fixed by https://chromium-review.googlesource.com/c/chromium/src/+/820353
,
Dec 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2a1c32dae820c7369767e868f29732670d8c1737 commit 2a1c32dae820c7369767e868f29732670d8c1737 Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Sat Dec 16 07:05:47 2017 Migrate some more automation events to AXEventGenerator. Only 6 new events that ChromeVox actually uses are migrated by this change. I added comments to the other events to keep track of which ones are candidates for migration or for removal in the future. Bug: 699438, 788893 Change-Id: Ica13cd36369770242a20954c020e80f0f1fbff63 Reviewed-on: https://chromium-review.googlesource.com/820353 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#524598} [modify] https://crrev.com/2a1c32dae820c7369767e868f29732670d8c1737/chrome/renderer/extensions/automation_ax_tree_wrapper.cc [modify] https://crrev.com/2a1c32dae820c7369767e868f29732670d8c1737/chrome/test/data/extensions/api_test/automation/tests/desktop/hit_test.js [modify] https://crrev.com/2a1c32dae820c7369767e868f29732670d8c1737/chrome/test/data/extensions/api_test/automation/tests/tabs/hit_test.js
,
Dec 22 2017
,
Jul 30
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Dec 6 2017Status: assigned (was: Untriaged)
This is because you are doing something like: <input id="text" type="text"></input> <script> var textFieldNode = document.getElementById('text'); textFieldNode.addEventListener('keypress', function() { textFieldNode.setAttribute('aria-invalid', false); }); </script> Assigned to dmazzoni@. Let's suppress invalidStatusChanged when aria invalid hasn't changed.