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

> If we are to define the behavior in a normative way, we had to use such a list in the spec for the purpose of the normative explanation.

Why?  If we can define an algorithm that finds the next element to focus given the current focused element, we can define a total order for all focusable areas.

>  I think the critical bit is that people get the same result at the point where someone cares about interoperability, not that the code paths in browsers are the same. So I think we're OK here…

The whole point of writing a spec is to define a behavior that can be implemented interoperably by different engines.  Unfortunately, the current spec text is so complex that I can't follow and I can't even reason about what the expected output is compared to what we do. 

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