New issue
Advanced search Search tips

Issue 794653 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
dmazz...@chromium.org
katie@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
STS
Team-Accessibility



Sign in to add a comment

[Select-to-Speak] STS doesn't work on second monitor

Project Member Reported by katie@chromium.org, Dec 13 2017 
Repro:
1. Load up multiwindow Chrome OS:
out/cros/chrome --remote-debugging-port=9999 --enable-experimental-accessibility-features --ash-host-window-bounds="801+0-800x800,1+0-800x800"
2. Open some browser window in the non-active window
3. Try using STS. It doesn't work.

Comment 1 by katie@chromium.org, Dec 14 2017 

Specifically, the onMouseDown event is not fired in the second window.

BUT if I patch the SelectToSpeakEventHandler->SelectToSpeak, in the first monitor it continues to work normally, and in the second monitor any actions are translated to the first monitor. So clicking and highlighting a region in the second monitor cause that mirrored region in the first to be selected.

Comment 2 by katie@chromium.org, Mar 9 2018

Labels: -Pri-3 Pri-2
Lower priority but still P2

Comment 3 by katie@chromium.org, Mar 19 2018

Components: UI>Accessibility>SelectToSpeak

Comment 4 by katie@chromium.org, Mar 19 2018

Components: -UI>Accessibility

Comment 5 by leberly@chromium.org, Apr 11 2018

Labels: M67test
Google Chrome 67.0.3383.0 (Official Build) dev (64-bit)
Google_Samus.6300.276.0
Chrome OS with flag enabled: #enable-experimental-accessibility-features

Works in Mirror mode with one or two monitors attached.
Doesn't work in extended mode with one or two monitors as indicated. 

Tested with Lulu, Samus, and Eve
►

Sign in to add a comment