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

@tkent-google I think that is the simplest design that could work. (Although I would change the name to be something less spec-focused and more intelligible to authors, but that doesn't matter for now.)

However, the above discussion revealed a few other possibilities:

- A tri-state attribute, to capture sequential-focus-navigable vs. not. See https://github.com/w3c/webcomponents/issues/762#issuecomment-414882495 .
- The TPAC discussion about platform convention matching. That would lead to an API that says something like `focusBehavesLike: "a"` or `focusBehavesLike: "button"`. Maybe we could come up with something more restrictive, like a set of a few archetypes (instead of allowing any tag name).

What do you think of these considerations? Maybe they are overcomplicating things, and we should just go with the simple boolean version.

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