- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 23:36:32 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Proposal for Navigation Controls`, and agreed to the following: * `RESOLUTION: Add navigation controls media query to MQ 5` * `RESOLVED: Add navigation controls media query to MQ 5` <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: Proposal for Navigation Controls<br> <AmeliaBR> github: https://github.com/w3c/csswg-drafts/issues/4187<br> <AmeliaBR> TabAtkins: Request for a way to tell if there is a back button or similar (e.g., PWA shells don't always have this), as a media query. Normal browser it would be true. PWA may be false, so you might want to add a back button in your page UI.<br> <florian> q+<br> <AmeliaBR> … For now, the request is only for back button, but the proposal is designed in an extensible way.<br> <AmeliaBR> dino: I don't understand the scope of "back button". Would a back-swipe gesture count? Generally support the idea, but we need to define it.<br> <AmeliaBR> … I can also see other use cases, like is there a share button?<br> <myles> Q+<br> <AmeliaBR> TabAtkins: Question on back swipe is interesting. Not all UI options are equal. Keyboard controls might not be well known. But depends on the platform.<br> <jensimmons> +1 to being generic... not too focused on How People Do Things in 2019.<br> <AmeliaBR> dino: That's just an example. My concern is that the query should focus on the functionality rather than the "button" nature.<br> <astearns> ack florian<br> <Rossen_> q+<br> <dino> oops. forgot about queuing :) sorry.<br> <dino> i just bullied my way in<br> <AmeliaBR> florian: Individual parts of the media query are useful. But how would it be collapsed to a boolean level, without breaking extensibility?<br> <astearns> ack myles<br> <AmeliaBR> TabAtkins: Current proposal is boolean means any navigation control, of which back button is the simplest. If we can't make that assumption, that the boolean mode is probably meaningless.<br> <AmeliaBR> myles: Some browsers are designed as standalone apps; other browsers integrate with a system, like an iOS webview. Whether there's a backbutton or not depends on the embedding app. Webview doesn't know, may be difficult to implement.<br> <AmeliaBR> TabAtkins: In that case, if the rendering agent doesn't know, they should probably be conservative & assume there isn't anything.<br> <AmeliaBR> florian: And maybe embedded web views could add an API for the environment to tell them if they're handling navigation.<br> <AmeliaBR> myles: that doesn't help with existing apps<br> <astearns> ack Rossen_<br> <AmeliaBR> florian: But it could help in combination with sensible defaults.<br> <AmeliaBR> TabAtkins: And the default wouldn't be any worse than today.<br> <AmeliaBR> Rossen_: Is there a reason we're only talking about back button right now & not navigation controls as a group?<br> <AmeliaBR> TabAtkins: No reason to avoid other features. It's just that back-button has the strongest use case & is the one that is most commonly available.<br> <AmeliaBR> … But I made sure syntax would work with other buttons, too.<br> <AmeliaBR> q+<br> <AmeliaBR> … If we find anything that is really important we can add them too.<br> <drousso> q+<br> <AmeliaBR> Rossen_: If we are only doing back-button for now, why not just use that in a boolean sense?<br> <AmeliaBR> … I didn't want "any"/"none" because that could be more complicated for adding things.<br> <fantasai> ScribeNick: fantasai<br> <fantasai> AmeliaBR: Would a URL bar be included inside this general concept of navigation controls?<br> <fantasai> TabAtkins: If people think that's a useful thing to expose, sure<br> <fantasai> TabAtkins: number of possibilities we could<br> <fantasai> AmeliaBR: URL bar allows copy/paste of current URL and also allows navigation<br> <fantasai> AmeliaBR: also can be used to share<br> <drousso> dino i am too<br> <fantasai> TabAtkins: Interesting question of whether that should be distinct from share button<br> <astearns> ack AmeliaBR<br> <fantasai> florian: Wrt URL bar, I could imagine a UI which has URL bar only but not back button<br> <AmeliaBR> ScribeNick: AmeliaBR<br> <fantasai> florian: so assumption of always having a back button might not be correct<br> <AmeliaBR> TabAtkins: Theoretically, but I don't think that will happen<br> <AmeliaBR> florian: without a time machine<br> <astearns> ack drousso<br> <AmeliaBR> drousso: One clarification: Are we talking about the *presence* of these buttons, or whether they are enabled? E.g., in a new tab, back button is disabled.<br> <AmeliaBR> TabAtkins: I could be convinced either way, I think it's best to say "is it present", regardless of whether currently disabled. Probably don't want to toggle this on and off a lot. Might be used via JS to download extra scripts.<br> <AmeliaBR> AmeliaBR: What is the request at this time?<br> <AmeliaBR> TabAtkins: To add to draft. Can discuss specifics later.<br> <AmeliaBR> astearns: Any objections to adding to a media queries draft?<br> <AmeliaBR> (silence)<br> <AmeliaBR> RESOLUTION: Add navigation controls media query to MQ 5<br> <tantek> tries to catch up<br> <fantasai> RESOLVED: Add navigation controls media query to MQ 5<br> <AmeliaBR> astearns: We should also get in touch with the original proposer (fallaciousreasoning) for giving credit.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4187#issuecomment-528132578 using your GitHub account
Received on Wednesday, 4 September 2019 23:36:33 UTC