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

@Alice wrote:

> I asked a colleague who works in front-end development, and they noted that not having a programmatic focus state means there is extra (and thus potentially error-prone) work when you want to move focus to something but not have it remain user-focusable after focus moves away. Maybe the solution there is an option to focus() to override the focusability bit?

How would that be different than making unfocusable custom elements still be programmatically focusable? Wouldn't it cause all the same focus problems @rniwa mentioned on the Microsoft Office 365 web app?

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