Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774)

I guess I don't understand how delegatesFocus is supposed to work and why the introduction of delegatesFocus changed tabIndex's semantics. I read #399 changed tabIndex's semantics because we wanted a feature "make everything of this custom element/shadow tree non-tab-focsable"? But isn't that what delegatesFocus=false does for us?

My intuition:

* If I want a custom element where neither the host nor its shadow content are tab-focusable: tabIndex=-1 on the host and delegatesFocus=false on the root.

* If I want a custom element where the host isn't tab-focusable but its shadow content **is**:
tabIndex=-1 on the host and delegatesFocus=true on the root.

The shadow host could then be a \<div\> where Shadow DOM content overflows (a scrollable div). Still, an author could decide to eject the \<div\> from the tab order but leave its [shadow] content in. 

-- 
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/774#issuecomment-440621570