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

Safari's behavior is that by default only form controls are tab focusable. Option + tab would focus every element that's focusable by default like link elements. Separately, every non-editable form element like buttons or input[type=submit] is *not* mouse focusable. In order to correctly describe WebKit's behavior, we'd need to be able to differentiate four states:
 * Editable form controls - tab & mouse focusable
 * Non-editable form controls - tab focusable but not mouse focusable
 * Links - option+tab focusable and mouse focusable
 * Everything else - not tab or option+tab focusable by default

Note that the user can override the behavior of tab key to be more like option+tab in Safari's preferences.

> we can do that by using an enum instead of a boolean

I think enum value is problematic because that would mean that whenever a new platform shows up, or the platform convention changes, websites may need to adopt the change. Also, I don't think hard-coding the list of things Safari do today to the web platform is a good idea either. Specifying relative to builtin elements is an interesting idea although it's hard to differentiate editable input from non-editable input but perhaps input is an odd case due to its behavior completely changing based on `type` attribute.

-- 
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-488873615