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

Having four options plus an extra boolean seems more complicated than having four options (if we need to add back `programmatic`; likewise for 3+boolean vs 3 if we don't). And the `auto` vs `sequential` distinction seems hard to understand from the names and descriptions. Seems like it will lead to lots of authors carelessly choosing `sequential`, since authors won't know what "up to the UA" will actually do, and thus custom controls won't actually play nice with platform conventions.

I think we do want to allow people to be able to create their own elements that accept text input. Note that, much like list boxes or pop-ups on the Mac, these may not actually be text editable. One obvious example would be a non-editable multicolumn list views that supports typeahead.

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