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

My thinking around tabbable was about the naming reflecting the default behavior, with the hope that it would make web developers also pick the correct default for their control. Users can override non-tabbable to be tabbable.

I cannot reach the first control in `data:text/html,<input type=range><input>` with a tab in Safari, though I can in Chrome/Firefox. And yeah, `<select>` can be reached.

If we want to go for naming after behavior, is the distinguishing factor text input perhaps (you can search a `<select>`), but cannot search a `<input type=range>`? (Although if you give a `<input type=range>` labels through `<datalist>` (not widely supported I think), is it really that much different?)

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