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

To me, `tabindex` only affects the node, not the subtree. 

I may wish to have a programmatically focusable custom element host, with focusable children. I would achieve that by placing `tabindex="-1"` on the host, so it's not in my natural tab order, but is available to me to place the users focus on if I choose to, in the user flow / interaction.

It shouldn't also remove all subtree items from being focusable too, even if they are in that hosts shadow. That should be left up to delegateFocus IMO

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