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

@bicknellr when `<slot>` has fallback contents and it does not have assigned nodes, the slot is a scope owner and tabindex within the slot makes sense.

In your case, `#shadow-slot-input-A` and `#shadow-slot-input-B` will be visited sequentially within the slot.  As the slot has tabindex 4, the sequence in the shadow root is `#shadow-input-A`, `#shadow-input-B`, `<slot>`, `#shadow-input-C`, `#shadow-input-D`.

Therefore the combined sequence when the slot has no assigned nodes is  `#shadow-input-A`, `#shadow-input-B`, `#shadow-slot-input-A`, `#shadow-slot-input-B`, `#shadow-input-C`, `#shadow-input-D`, for `#x-custom-B`.

The order for `#x-custom-A` is correct.


In the spec, In section 6.3 Step 2, all elements in the tree will be divided into scopes, and descendants of `<slot>` element which will become fallback content will belong to the slot scope (Specifically, Step 2, 2.1.4.2. "Otherwise append ELEMENT to SCOPE-MAP[CURRENT]").

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