- From: Simon Taggart <notifications@github.com>
- Date: Mon, 26 Nov 2018 16:17:02 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 November 2018 00:17:23 UTC
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
Received on Tuesday, 27 November 2018 00:17:23 UTC