New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 916423 link

Starred by 2 users

Issue metadata

Status: Available
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: ----
Type: ----
Team-Accessibility



Sign in to add a comment

Assistant reacts to ChromeVox on the same device

Project Member Reported by ginko@google.com, Dec 19

Issue description

Chrome Version: Before 71
OS: Chrome

What steps will reproduce the problem?
(1) Activate ChromeVox (Ctrl+Alt+Z)
(2) Open launcher
(3) Type in "hey"
(4) Press down

What is the expected result?
Normal reading of the "hey" google search entry

What happens instead?
Assistant recognizes ChromeVox as a user and executes a query

 
Cc: aprilkuo@chromium.org omrilio@chromium.org
Owner: xiaoh...@chromium.org
Components: -UI>Accessibility -UI>Shell>Launcher UI>Accessibility>ChromeVox
There are multiple features in the works that would fix this issue.
1. We are introducing voice id, once user is enrolled, it should only respond to the corresponding user's voice.
2. Unified audio focus. With this feature, Assistant should be able to duck other audio when it's listening.
Status: Available (was: Untriaged)
Great, do you have any update on timing of those launches? Also, the other way around this is to use headphones to listen to ChromeVox. 
both are scheduled for M73

Sign in to add a comment