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

Issue 672362 link

Starred by 6 users

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Multitouch shorcut starts chromevox: makes Android apps unusable

Reported by marc.her...@gmail.com, Dec 8 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9000.15.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.12 Safari/537.36
Platform: 9000.15.0 (Official Build) dev-channel lulu

Steps to reproduce the problem:
1.Start any Android app 
2.Touch and hold two fingers in two place. Hear countdown. Chromevox starts
3. Android app becomes unusable

What is the expected behavior?
No chromevox on Android apps.

What went wrong?
Chromevox starts on Android

Did this work before? N/A 

Chrome version: 56.0.2924.12  Channel: dev
OS Version: 9000.15.0
Flash Version: Shockwave Flash 23.0 r0

This is a very recent regression from the previous version on the dev channel with had a build date a few weeks older than this one.
 
> This is a very recent regression from the previous version on the dev channel with had a build date a few weeks older than this one.

- This is a regression probably just because this multi-touch-and-hold shortcut is new. I just reverted to the beta channel and this shortcut isn't there yet:
Version 55.0.2883.82 beta (64-bit)
Platform 8872.67.0 (Official Build) beta-channel lulu

- This brand new shortcut does exactly the same than Ctrl-Alt-Z: it merely starts Chromevox. That's enough to make Android games totally unusable.
- Holding two fingers on Android is no different than holding two fingers outside Android. Too bad Android apps - especially games - rely on multi-touch already.
- With respect to this bug I found no difference between Chromevox classic versus Chromevox next.

See related (and older)
 Issue 653201  Stop chromevox audio when switching to arc app
Cc: drinkcat@chromium.org
Components: Platform>ARC
Cc: yawano@chromium.org erosky@chromium.org
Some more testing

- I tried to reproduce on cyan with very close Version 56.0.2924.20 beta (64-bit)
Platform 9000.22.0 (Official Build) beta-channel cyan; however no such multitouch shortcut there.

On the original lulu system and image:
- The same multitouch shortcut and audio countdown do not only start but also stop chromevox, exactly like Ctrl-Alt-Z does
- The multitouch shorcut starts Chromevox whether play store is enabled or not. The shortcut is active even in Guest mode. Doesn't seem to know or care about ARC (basically the issue).
- This shortcut triggers even with one finger on one android app and another on a browser window

I manually booted lulu from USB with version 56.0.2924.20 (Official Build)
      Platform 9000.22.0 (Official Build) dev-channel lulu test

... and it looks like this will be fixed once .20 hits lulu's dev channel just like it already did for cyan's. Until this happen Android will stay unusable on lulu.
Components: -UI UI>Accessibility
Owner: dtseng@chromium.org
Status: Assigned (was: Unconfirmed)
Owner: dmazz...@chromium.org
assigning to dmazzoni@ to ensure it was reverted.
Status: Fixed (was: Assigned)
This was reverted. I'm going to look into enabling it only for Chromebox for Meetings, and/or making it require three-fingers, or something else.

Perhaps tap once in each corner or place two fingers down a hold in any corner.
Not sure how I missed this:
 Issue 667439 	Disable ChromeVox touchscreen enable in M56

BTW, is there a newer version of this? https://googlechromereleases.blogspot.com/search/label/Chrome%20OS+Dev%20updates

The last entry there is dated October 18.
https://omahaproxy.appspot.com/ shows you what version of Chrome or Chrome OS is currently live.

It looks like on Chrome OS, dev channel is on 56.0.2924.12, which was updated on 12/03/16.

I'm not sure how often that blog is updated. My guess is that updates are not mandatory for dev channel, just stable.

Very useful thanks; everyone should know about omahaproxy.

I just reset a cyan and switched it the dev channel to confirm it's on 56.0.2924.12 too and is affected by this too; it's not specific to lulu like I thought it might be.

So long story short all Android apps that depend on multitouch are unusable on the dev channel right now.

Comment 15 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58
Status: Verified (was: Fixed)

Sign in to add a comment