Re: [webcomponents] Proposed change for Focus Navigation (#381)

It looks iterative reviews won't work well if completely different structure is suggested.

I've written the draft following your suggestion:
https://docs.google.com/document/d/1mNV2Z231SrAZuMJvBVNfVNHfULkMwUZOZ75vZM1K9zY/edit?usp=sharing (anyone can comment)

For the 3rd algorithm (ordering) in the comment,
for document/shadow root scope, the order is probably obvious (tree order),
but for slot scope (not fallback content scope) the traversal order is depth-first
search on result of getAssignedNodes()?

In addition, do we want to describe how to compare 2 focusable areas with tabindex here
to get the scoped order of the sequence?

That would add almost dead-copy of [HTML 6.4.3](https://html.spec.whatwg.org/multipage/interaction.html#the-tabindex-attribute) and
super redundant.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/pull/381#issuecomment-188134052