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

@annevk  It might be that the three-way distinction between keyboardable controls, non-keyboardable controls, and totally unfocusable non-controls is sufficient (since these distinctions seems to be present in other browsers). We may not need to maintain the distinction between links and non-keyboardable controls for custom controls.  i.e. never let custom controls be link-like in the specific way that makes a difference only in Safari.

(How focus works in AppKit and UIKit is kind of confusing. I'm asking folks who know more how this customization is normally done. From quick testing, it looks like other apps include native link-looking controls when full keyboard access is enabled, and we'll likely review this behavior in WebKit now that it's come to our attention anew.)

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