Re: [w3ctag/design-reviews] Spatial Navigation (#287)

Hey all,

Thanks for filing a review. We noted excitement about this at TPAC and are glad to have the opportunity to work with you on this. Thanks also for the detailed explainer.

We spoke with folks working on this recently in an ad-hoc discussion, wanted to get some of these thoughts written down.

[Hostile iframes](https://github.com/WICG/spatial-navigation/issues/58) seem like a serious issue, but we're curious about how they're different to other sorts of focus capturing issues; e.g. the fullscreen API. Those APIs preserve a keyboard shortcut to allow escape. Is something like thpossible? The proposed feature policy seems like a promising direction.

The traversal (distance computation) algorithm seems to have properties which result in unexpected (at least from a user's perspective). A potential improvement has been noted in your issue tracker - https://github.com/WICG/spatial-navigation/issues/122#issuecomment-433053747 although there are probably better ways to approach this.

Are Focusable Areas seem to have a correspondence with Intersection Observers. Has a similar set of [rootMargin and threshold options](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#Creating_an_intersection_observer) been considered?

An interesting point of feedback from other communities was around the right-left (start on one element, traversal, where focus does not return to the element the user came from, this seems like a limitation that should either be addressed or explicitly noted.

Minor nit: The spec text for defining P1 and P2 could be clearer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/287#issuecomment-434753630