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

Seeing https://github.com/whatwg/html/pull/5120 brings up an issue that `"unfocusable"` being the default is a bit strange. In particular, currently `<x-element tabindex="0">` will be focusable. But then we have `internals.focusBehavior === "unfocusable"`, so it is both focusable and unfocusable, which is confusing.

Given this, I think maybe `focusBehavior = "none"` is better than `focusBehavior = "unfocusable"`. And we should probably explain that tabindex takes precedence over all of these? I'm not sure where that last part would fit in the spec, if it does.

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

Received on Tuesday, 3 December 2019 16:18:34 UTC