Re: [w3c/webcomponents] Algorithms in 6.3. Sequential Focus Navigation are too complex (#496)

> I don't know if this is really a concern or not, but it seems odd that slot fallback content doesn't also get put into a separate scope. Particularly, this means that elements can be 'inserted' into the surrounding sequential focus order when a slot doesn't have fallback content.

I am aware these cases, and I thought these cases should be handled correctly in the spec.
If we can not read that from the spec, it should be considered as a bug of the spec.

At least, Blink should handle such a case correctly, Let me check that again later.

It would be better that the example should cover these cases to clarify that.



---
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/496#issuecomment-228234147