New issue
Advanced search Search tips

Issue 871225 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 7
Cc:
katie@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

STS touchscreen: single tap interpreted as selection when button is on, unable to navigate UI

Project Member Reported by leberly@chromium.org, Aug 6 
Google Chrome	70.0.3511.0 (Official Build) canary (64-bit)
Firmware Version	Google_Eve.9584.160.0

Steps to reproduce:
# Turn on Select to Speak in Settings > Manage Accessibility Settings
# Fold into tablet mode or only use touchscreen
# Press button to start ability to speak
# Tap on another open tab to be able to read something on that page
Expected: single tap doesn't count as a selection, I should need to drag to do that
Actual: a single tap counts as selection, unable to change tabs etc. while feature is invoked

Comment 1 by leberly@chromium.org, Aug 6 

Further side effects:

Location of tapping becomes extremely important. I could tap just off the edge of a text node and nothing is read. If I had to drag to get it reading, this becomes less of a problem.

Automatic clicks starts reading as soon as click is registered.

Comment 2 by leberly@chromium.org, Aug 6 

Possible solution: implement Feature request: STS touchscreen "sticky mode" to be able to make many selections in a row
https://bugs.chromium.org/p/chromium/issues/detail?id=871236

Comment 3 by katie@chromium.org, Aug 6 

This is actually working as we intended originally -- it's the touch-only equivalent of search+click. But it makes sense that it's hard to use especially with navigation.

Comment 4 by leberly@chromium.org, Aug 6 

Here is a video showing the bug and the fact that when STS is being invoked, the tap is not recognized as a tap, making it a bit confusing to use.

https://drive.google.com/file/d/1B-jyNmWqqF3mvMWrvyGAJCCFYuuwJqad/view

Comment 5 by katie@chromium.org, Aug 7

Status: WontFix (was: Available)
I'm going to close this since it's working as intended. Whether there should be a sticky mode can be tracked in the FR bug you added in #2.
►

Sign in to add a comment