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

Well, the problem with the current spec is that it creates a list of elements and transforms multiple times into the final sequence of elements that define the tab sequencing order.  Having to construct such a list each time tab focusing order is changed, or even to retain such a huge list of elements is way too efficient for implementation purposes.

What we need instead is an algorithm that defines how to find the next sequentially focusable element.  With the right set of abstractions, that algorithm can be defined a lot more concisely.  I'll get around to doing that once I took care of more urgent matters.

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