New issue
Advanced search Search tips

Issue 874250 link

Starred by 1 user
Status: Assigned
Owner:
katie@chromium.org
Cc:
leberly@chromium.org
jamescook@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Select-to-speak sometimes doesn't work in shortcut viewer dialog

Project Member Reported by jamescook@chromium.org, Aug 14 
ToT chrome on caroline. This has the new M70 "app" version of the shortcut viewer dialog.

* Turn on select-to-speak
* Ctrl-Alt-/ to open shortcut viewer dialog
* Click on select-to-speak shelf icon, then click on parts of the dialog

Sometimes it speaks and sometimes it doesn't. When it doesn't the pink selection rectangle appears around the cursor, but it's only ~16x16 pixels (looks like it has an empty size).

katie/leberly - any advice on troubleshooting this? I'm having a hard time figuring out how I get into this state.

Comment 1 by jamescook@chromium.org, Aug 14

Cc: -katie@chromium.org jamescook@chromium.org
Components: -Internals>Services>Ash UI>Input>KeyboardShortcuts
Labels: -Pri-1 -Proj-Mash-KSV Pri-2
Owner: katie@chromium.org
Actually, it's not related to the app version. You can disable "Keyboard shortcut viewer mojo app" in about:flags and see the same behavior.

Details:
* Clicking on things in the scroll view doesn't work (e.g. "Copy selected content to the keyboard")
* Clicking on items in the category list on the left works, but there is a significant delay the first time you click (seconds). This can make it look broken.

To katie, since I don't think this is a mustash/mash/mojo app problem. Perhaps the items in the list need a11y annotations? Maybe the delay is related to extension loading?

Comment 2 by katie@chromium.org, Aug 14 

The delay is probably related to loading the Text-to-Speech extension. Especially if you can reproduce it only after the first time speech occurs -- for example, if you toggle Chromevox before using Select-to-Speak and both are using the same voice, then Select-to-Speak should not have a delay.

Native UI doesn't have text/word boundaries populated in accessibility, so highlighting won't work in STS. This is a known bug.

Otherwise, I'm not seeing the same issues in xbuddy://remote/nocturne/latest-canary/test -- After the initial delay in reading (less than a second for me), I can read text like "copy selected content to the keyboard" and click on items in the category list.
►

Sign in to add a comment