Issue metadata
Sign in to add a comment
|
Pressing t to RT a tweet does not read dialog box that pops up using CVox
Reported by
ni...@jaberspace.com,
Oct 24 2016
|
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 56.0.2897.0 Reproduction Steps: 1. twitter.com 2. j to find a tweet to RT 3. t to retweet Expected: Chromevox would read the message that pops up asking me to choose an action. Actual: Nothing is read, but not sure if this is an issue on Twitter's end or one with CVox.
,
Oct 24 2016
They read the box that comes up and allow the user to focus the buttons with a press of the Tab Key. These buttons include cancel or retweet.
,
Oct 24 2016
,
Oct 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6e3a3a84756c2ee9d06f9c0766b694ea6520f368 commit 6e3a3a84756c2ee9d06f9c0766b694ea6520f368 Author: dtseng <dtseng@chromium.org> Date: Tue Oct 25 18:21:43 2016 Fix bad focus state tracking Since |automationUtil.updateFocusedNode| gets called both from the client |getFocus| api as well as by onAccessibilityEvents (when receiving focus events), we sometimes discarded focus events because we updated focus when a client called getFocus before the actual focus event fires. In the attached bug, we fire a childrenChanged event where we already implicitly changed the focused node. On an event handler, a client calls getFocus, updating the focused node. The next event, the actual focus event, is discard incorrectly. BUG= 658621 Review-Url: https://codereview.chromium.org/2446263002 Cr-Commit-Position: refs/heads/master@{#427417} [modify] https://crrev.com/6e3a3a84756c2ee9d06f9c0766b694ea6520f368/chrome/renderer/resources/extensions/automation_custom_bindings.js
,
Oct 26 2016
,
Oct 31 2016
verified on 56.0.2903.0 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chaok@google.com
, Oct 24 2016