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

@rniwa @othermaciej How does Darwin deal with developer-introduced controls and introducing new controls of its own? Is there a system in place or are applications expected to be updated?

What would your preferred approach be here? Above you mentioned four categories being too few as it would not give enough room for more drastic behavior changes. Should we have a value for each thing you can consider a control today and let user agents map those as they see fit? If yes, I think I agree with the potential weirdness of using ARIA's `role` for this, even if somewhat fitting, as it would be the first time we attach semantics to it. Having an equivalent API with effectively the same values isn't that great either, but perhaps we can have something that sets both at once or some such.

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