W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

Re: [csswg-drafts] [css-ui-4] Make directional navigation more composable

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 07 Nov 2017 18:42:54 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-342581100-1510080173-sysbot+gh@w3.org>
The Working Group just discussed `https://github.com/w3c/csswg-drafts/issues/1910`.

<details><summary>The full IRC log of that discussion</summary>
&lt;florian> Topic: https://github.com/w3c/csswg-drafts/issues/1910<br>
&lt;gregwhitworth> jcraig: this will fail on its own in the weeds<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/1910<br>
&lt;gregwhitworth> florian: one of the weird things that we have with arrow keys, it lets you define where you should focus to<br>
&lt;gregwhitworth> florian: what happens if the element where you want to go to isn't focusable<br>
&lt;gregwhitworth> florian: what is currently defined is that if the user wants to go there we should make it focusable<br>
&lt;gregwhitworth> florian: these days many/most are built are out of components<br>
&lt;gregwhitworth> florian: this may allow the browser to go the "right" and then seek for the first focusable element<br>
&lt;gregwhitworth> florian: if you're the author you can point to what's there, if your using a component and you don't know what's there maybe a heuristic is better<br>
&lt;gregwhitworth> tantek: as an author you may want to use a seamless iframe but you don't know what's on the other side. I don't think we can determine the best behavior<br>
&lt;gregwhitworth> tantek: since you mentioned components, I think we shouldn't be solving this in isolation<br>
&lt;gregwhitworth> florian: I'm not disagreeing with what you state, I'm not sure how that answers my question<br>
&lt;gregwhitworth> tantek: I'm saying this discussion doesn't belong in CSSWG<br>
&lt;gregwhitworth> smfr: so are you saying these props don't belong in CSSUI<br>
&lt;gregwhitworth> smfr: to me, it sounds like spacial navigation would be in its own spec rather than here in its own naïve form<br>
&lt;gregwhitworth> florian: do you think there is a potential case where the focusable behavior is what you would want?<br>
&lt;gregwhitworth> tantek: very unlikely<br>
&lt;gregwhitworth> florian: I think searching inside of that makes sense and is uncontroversial<br>
&lt;gregwhitworth> tantek: you're asking about something n the weeds and I'm not sure it helps/hurts and I think we should move this to a different arena<br>
&lt;gregwhitworth> astearns: is anyone lining up to implement this improvement, then I think there would be a case to make a change to the spec<br>
&lt;gregwhitworth> astearns: if this is just an academic change, what's the point?<br>
&lt;robdodson> (sorry for speaking out of turn) but the notion of creating focus "groups" seems to already exist today with Shadow DOM. jsbin.com/lidaguf/edit?html,output<br>
&lt;gregwhitworth> florian: the fact that, it works poorly when you have blackbox component which was mentioned by Blink<br>
&lt;gregwhitworth> tantek: I don't think it's experimental<br>
&lt;gregwhitworth> astearns: *reads rob's comment*<br>
&lt;gregwhitworth> robdodson: the notion of focus groups kind of exists already, that will allow once focus is within that shadow root boundary<br>
&lt;gregwhitworth> robdodson: the notion of the grouping kind of exists if you're willing to use shadow dom<br>
&lt;tomalec> AFAIK, Shadow DOM also propagates, kind of scoped focus, to elements distributed via `&lt;slot>`<br>
&lt;tantek> issue filed: https://github.com/w3c/csswg-drafts/issues/1948<br>
&lt;gregwhitworth> florian: what I was thinking of trying to specify if you focus that non-focusable element - if there is tabindex, etc use that<br>
&lt;tantek> I mean GH issue filed https://github.com/w3c/csswg-drafts/issues/1948<br>
&lt;tantek> " [css-ui-4] Spatial Navigation needs a new home in WICG #1948 "<br>
&lt;gregwhitworth> florian: since we don't seem to have consensus can I suggest a lighter one to make a change to what we agree is stupid"<br>
&lt;gregwhitworth> ???: What do we all agree is stupid?<br>
&lt;gregwhitworth> ???: Currently you only seem to say that you should look for tabindex<br>
&lt;gregwhitworth> florian: or is a button, etc<br>
&lt;astearns> s/???/bradk/<br>
&lt;gregwhitworth> florian: it seems very weird to me that something is focusable will take you to something that isn't focusable but with a tab key you can't<br>
&lt;gregwhitworth> florian: that's weird<br>
&lt;gregwhitworth> astearns: since we're not closing, let's table the issue for now<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1910#issuecomment-342581100 using your GitHub account
Received on Tuesday, 7 November 2017 18:42:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 November 2017 18:42:58 UTC