Re: [webcomponents] Update Section 6.2 Focus Navigation to reflect TPAC discussion (#375)

I agree that introducing scope for a slot is surprising for component users in some cases.

In fact, that's exactly the reason I could not take this approach in the past in Blink: This approach would break tabindex semantics for `<details>/<summary>` elements because `<details>/<summary>` is using Shadow DOM in Blink.

However, I think pros is much bigger than cons.

The cons happens in the limited case, I think, if the all of the following conditions are met:

- If a shadow host is not a custom element
- A shadow host's child does not use a slot attribute, and it is assigned to the default slot
  
In other cases, developers can be aware that that "This tabindex is used in assigned slot's scope, rather than the current component tree's scope", I think.
    
Having said that, I still think that pros is much bigger than cons. If there is a way to avoid this cons somehow, it would be nice.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/375#issuecomment-179029658