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

> > it's also a bit problematic to hard code exactly the set of behaviors Safari has because we need to design this to be forward compatible.
> 
> I don't follow - I'm suggesting the opposite of that: the developer chooses only "always tabbable" or "UA decides", and then the UA decides based on any set of signals it feels is appropriate.

Alice's idea looks to work well.  The current Safari behavior can be explained by difference of elements' default roles.

The only concern is that a future platform might introduce an exotic focus behavior for elements which can not be distinguished by ARIA roles.  e.g. 
 - New focus behavior only for `<input type=date>`, which has no specific ARIA role.
 - New focus behavior only for `<input type=reset>`, of which role is `button` and there are other elements of which roles are `button`.

Even if a custom element author wants a custom element to follow such focus behavior, it's unable to signal it with ARIA roles.  UAs need to find other signals.  The custom element would have the default focus behavior if there are no such signals.







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