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

 From [this gist](https://gist.github.com/alice/b83a9d315a4aae30aabbe27710e91c52), Alice wrote:

> I think we can get away with two states, with several caveats.
> 
> The states would be:
> 
> `focusable` (or `auto`, or...)
> `default` (or `unfocusable`, or...)
> 
> The caveats:
> 
> `unfocusable` custom elements would still be programmatically focusable.

So, custom elements set as `unfocusable` would not be in the tab order, but would achieve still focus if the author called the `.focus()` method on the custom element. Correct?

> Safari would need to determine click/sequential focusability of focusable elements based on ElementInternals role.
> 
> [Another gist](https://gist.github.com/alice/bac0f6741b852f6e87f53e028efbde2f) gives an example of using these two states to manage focus within a complex custom element.

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