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

@cynthia and I are looking at this in a breakout at the TAG's Reykjavík face-to-face meeting.

One concern that I have is the bit at the very end of the [explainer](https://drafts.csswg.org/css-nav-1/explainer) about spatial navigation and HTMLFormElement, which links to a [separate document](https://github.com/WICG/spatial-navigation/wiki/Spatial-Navigation-Guideline-for-HTMLFormElement).  I have a few concerns here:
* form controls aren't necessarily implemented using shadow DOM, but might be in the future.  However, there probably should be text saying both what happens for form controls and for shadow DOM.
* whether it's using shadow DOM or not, it's important not to break encapsulation.  This means that the insides of the form control or shadow tree can't be visible to the outside.  Yet it still should be possible to navigate within the parts of the shadow tree or form control if there are multiple parts.  So it seems like perhaps what spatial navigation exposes *inside* of a shadow tree should probably be different from what it exposes outside a shadow tree.  That is, perhaps there should be a way for the shadow tree to "capture" some of the spatial navigations to be movement inside of it, and then in other cases allow the navigations to move outside of it.  But it's probably worth running this past folks involved in w3c/webcomponents.
* the guidelines on dealing with form controls seem a bit too prescriptive -- they seem to assume particular designs for form controls that may not be the case

(Note that these comments are based on the explainer; I haven't looked at the spec.)

@cynthia will add some comments on other topics that we looked at.

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

Received on Thursday, 23 May 2019 10:10:09 UTC