Issue metadata
Sign in to add a comment
|
Chrome OS touch exploration should not hover on a descendant of a button |
||||||||||||||||||||||||
Issue descriptionElements that are conceptually leaves, like focusable form controls, etc. - should be the target when doing touch exploration on Chrome OS. Right now if you have a <button> for example, you can tap on the static text inside the button, but we should be focusing on the button instead.
,
Sep 28 2017
See https://bugs.chromium.org/p/chromium/issues/detail?id=767335#c8 for real example.
,
Nov 14 2017
Any progress? ChromeVox shouldn't explore inside role = "button" element.
,
Nov 15 2017
,
Nov 17 2017
dmazzoni@ can this be done in M64?
,
Dec 18 2017
I can't reproduce this on trunk, can you clarify if there's still an issue with ChromeVox focusing on a descendant of a button or if this can be closed?
,
Mar 7 2018
Sorry to take the bug by mistake.
,
Oct 18
I can't repro this anymore. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by oka@chromium.org
, Sep 28 2017