Issue metadata
Sign in to add a comment
|
Reading next and previous post in Google Plus with Chromevox does not work as expected
Reported by
nimerjaber1@gmail.com,
Apr 21 2016
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 52.0.2712.0 Reproduction Steps: 1. Launch Chromevox 2. Navigate to plus.google.com 3. Press J to move to the next post or K to move to the previous post. Expected Result: Chromevox would read out the next or previous post. Actual result: Chromevox is silent. Note that this is with the new Google Plus interface.
,
May 12 2016
,
May 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a6d987106258a552e3da0cd1c7f5ac75151a30a2 commit a6d987106258a552e3da0cd1c7f5ac75151a30a2 Author: dtseng <dtseng@chromium.org> Date: Fri May 13 22:01:01 2016 Output divs using descendant nodes. Some sites contain complex divs which they focus in order to force output of rich content. Enclosed is an example similar to content found on Google Plus. BUG= 605396 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/1974963002 Cr-Commit-Position: refs/heads/master@{#393654} [modify] https://crrev.com/a6d987106258a552e3da0cd1c7f5ac75151a30a2/chrome/browser/resources/chromeos/chromevox/cvox2/background/live_regions_test.extjs [modify] https://crrev.com/a6d987106258a552e3da0cd1c7f5ac75151a30a2/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js [modify] https://crrev.com/a6d987106258a552e3da0cd1c7f5ac75151a30a2/chrome/browser/resources/chromeos/chromevox/cvox2/background/output_test.extjs
,
May 16 2016
,
May 18 2016
Checked on latest chrome 52.0.2739.0, 1.Enable Cvox next and open "plus.google.com" The Cvox is struck and nothing is reading out after opening Google plus.Even if we move to any other page also the spoken feedback doesn't read anything.
,
Jun 7 2016
,
Aug 19 2016
,
Sep 26 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by abodenha@chromium.org
, Apr 21 2016Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)