Issue metadata
Sign in to add a comment
|
ChromeVox touch: unable to tell where bezel begins when using explore by touch |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 69.0.3494.0 (Official Build) dev (64-bit), Firmware Version Google_Eve. 9584.160.0 Steps to reproduce: # Flip convertible ChromeVox into tablet mode # Turn on ChromeVox by holding both hardware volume keys for 5 seconds # Slide finger from outer bezel into the main touchscreen area; listen for earcon indicating crossing this threshold # Lift finger, tap anywhere on the outer edges of the screen on the bezel Expected: some way to know that you are touching a bezel, not a touchscreen Actual: no way of knowing. This is made much worse by flaky touch screen response in bug 869905 There may not be a technology solution for this so we might have to put this into a tutorial to explain what's happening.
,
Aug 3
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dd98e27d135a2c693b7988113e40f67002c40a63 commit dd98e27d135a2c693b7988113e40f67002c40a63 Author: David Tseng <dtseng@chromium.org> Date: Fri Aug 03 22:05:36 2018 Remove touch exploration corner pass through and screen enter/exit earcons Bug: 869921 , 854321 , 869955 Change-Id: I9d9ae5aa5c590cf0200e6953054dff1833fc7b76 Reviewed-on: https://chromium-review.googlesource.com/1161176 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#580666} [modify] https://crrev.com/dd98e27d135a2c693b7988113e40f67002c40a63/ash/accessibility/touch_exploration_controller.cc [modify] https://crrev.com/dd98e27d135a2c693b7988113e40f67002c40a63/ash/accessibility/touch_exploration_controller.h [modify] https://crrev.com/dd98e27d135a2c693b7988113e40f67002c40a63/ash/accessibility/touch_exploration_controller_unittest.cc
,
Aug 7
,
Aug 8
We've removed the touch screen enter/exit sounds. I consider hardware specific borders to be something we should learn about, but without explicitly calling it out, users will simply perceive those areas as empty space.
,
Oct 4
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Aug 2