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

@Alice wrote:

> `unfocusable` custom elements would still be programmatically focusable.

Above [you mentioned roaming/roving tabindex](https://github.com/w3c/webcomponents/issues/762#issuecomment-596372747) as the primary justification for programmatic focus, but most of the examples I've seen toggle the state of those sub-controls between `tabindex="0"` and `tabindex="-1"` effectively making them focusable and non-focusable. The portion of the control gets focused is always made focusable at the same time the author calls `.focus()`, right?

If so, maybe it's okay to force the author to make a custom element `focusable` before calling `.focus()`... Putting this limitation on custom elements may bring us back to a simpler boolean state: `focusable` or not.

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