Re: [csswg-drafts] [css-nav-1] Predefined algorithm for spatial navigation (#3964)

The CSS Working Group just discussed `Predefined algorithm for spatial navigation`, and agreed to the following:

* `RESOLVED: Add spatial-navigation-function to the spec`

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: Predefined algorithm for spatial navigation<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/3964<br>
&lt;heycam> jihye: in general, the focus move to the closest element from the currently focused element<br>
&lt;heycam> ... and in the spec the algorithm for how to find the closest element, there is a description about that<br>
&lt;TabAtkins> BTW: based on current discussion, I'm editting p-c-s to be "light | dark | bright", dropping the no-preference value (and defining that "light" should be what a lack of preference means).<br>
&lt;heycam> ... but some authors this kind of algorithm it's not suitable for them<br>
&lt;heycam> ... depending on their own layouts<br>
&lt;heycam> ... so there is some spatial nav API to help authors customize this algorithm<br>
&lt;heycam> ... but it's difficult to do this, since they have to interrupt the processing model of spatial nav<br>
&lt;heycam> ... the processing model means finding the best target<br>
&lt;heycam> ... starting from when the user inputs some information, finding the best target -- all that process is called "processing modeL"<br>
&lt;heycam> ... it's hard to interrupt that in the middle<br>
&lt;heycam> ... so it would be nice to have a new CSS property to provide another algorithm for spatial navigation<br>
&lt;heycam> ... this will increase flexibility of spatial navigation, and will help authors to implement it more easily<br>
&lt;heycam> ... I want to propose spatial-navigation-function CSS property, with two values<br>
&lt;heycam> ... normal, where focus will move to the closest one<br>
&lt;heycam> ... and grid, this will go to the most aligned element from the currently focused element<br>
&lt;heycam> ... the focus will go to a more obvious spatial navigation direction<br>
&lt;florian> q+<br>
&lt;heycam> ... there is a demo I attached in the GitHub issue<br>
&lt;Rossen_> Zakim, open queue<br>
&lt;Zakim> ok, Rossen_, the speaker queue is open<br>
&lt;florian> q+<br>
&lt;heycam> ... you can select normal or grid, and see how it works differently<br>
&lt;heycam> demo: https://raw.githack.com/WICG/spatial-navigation/develop/demo/calendar/index.html<br>
&lt;heycam> florian: bikeshedding aside, I'm supportive of having a property to switch how we calculate the distinace, how to pick<br>
&lt;heycam> ... I'm wondering if we have the right values in that list<br>
&lt;heycam> ... if we think we do, and implementors want to experiment with this, sure<br>
&lt;heycam> ... but there are a anumbe rof variants we can think of<br>
&lt;heycam> ... the ones proposed seem reasonable, but are they actually a good match?<br>
&lt;heycam> ... the alternative to normal, is that what authors really want?  we're lacking experience<br>
&lt;heycam> ... it's difficult to say "70% of people who have trouble with normal want this grid behavior"<br>
&lt;heycam> jihye: with grid, I'm communicating with framework team in LG.  this is their main request from them<br>
&lt;heycam> ... their main implementation is something like TV schedule web page, or TV content<br>
&lt;heycam> ... normally those kinds of pages, elements are grouped horizontall and vertically, so in that case moving the focus just horizontally or vertically is more important than moving to the closest one<br>
&lt;heycam> florian: for that reason, intuiitively the grid behavior makes sense to me<br>
&lt;heycam> ... if you have anecdotal evidence that authors want this, this is an improvement<br>
&lt;heycam> ... not quite as good as stats over many users but it's a start<br>
&lt;bkardell_> me wonders if he can reserve comments on this until post the next topic<br>
&lt;Rossen_> ack florian<br>
&lt;heycam> heycam: is that sufficient evidence to add it ot the spec?<br>
&lt;heycam> florian: we have some evidence it's wanted, and on the face of it is reasonable, so sure<br>
&lt;heycam> bkardell_: I would like to reserve comments until after the next topic, since they're related<br>
&lt;heycam> Rossen_: any objections to adding this to the spec?<br>
&lt;heycam> RESOLVED: Add spatial-navigation-function to the spec<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3964#issuecomment-499536668 using your GitHub account

Received on Thursday, 6 June 2019 15:10:56 UTC