Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762)

We have two categories of focusable elements in Chrome:

* Elements which supports  complex keyboard interaction while it's focused
  Text-field INPUTs, TEXTAREA, SELECT, contenteditable
  They are "Text boxes and lists" in macOS [Full Keyboard Access](https://support.apple.com/en-gb/HT204434#fullkeyboard) setting. 
  ```:focus-visible``` and ```:focus``` have same behavior.

* Elements which supports simple keyboard interaction.  e.g. Spacebar works as click.
  Buttons and links
  They are skipped in sequential focus navigation if Full Keyboard Access setting is "Text boxes and lists only".
  ```:focus-visible``` doesn't match to them if they are focused by mouse click.

If we support only these two categories, we should add a boolean flag like ```needsComplexKeyboardInteraction```.
Do we want to support a behavior other than these two categories?


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/762#issuecomment-484461545