[Webkit-unassigned] [Bug 225148] [selectors] :focus-visible and keyboard events

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=225148

--- Comment #19 from James Craig <jcraig at apple.com> ---
I wrote: 
> The spec text that is ambiguous to me is "supports keyboard input." For example, <select> (and custom ARIA equivalents) can support keyboard input in the form of arrow keys or typeahead to change selection. Does that ability necessitate `focus-visible` even though there is no [insertion caret or] text input "value" associated as with <input type="text">?

Rob wrote:
> The key phrasing here is "and the focused element does not support keyboard input". Since a div with a tabindex does not support keyboard input then it should not match :focus-visible when mouse-clicked. If, however, someone were to add contenteditable to the div, then it would meet the criteria and :focus-visible would match.

Some examples that may still be ambiguous in the spec phrasing.

<div tabindex="0" role="slider"> (with JS key handlers for arrows, home/end, etc)
<div tabindex="0" role="listbox"> (or individually as "option" role) (with JS key handlers for arrows and typeahead filtering)

Perhaps the way to move forward is with a more explicit definition of what it means to "support keyboard input"? Alternatively, Brian Kardell suggested we move forward by determining a list of what matches :focus versus :focus-visible. Potentially that would enumerate a number of these ambiguous examples.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210505/021efd2d/attachment.htm>