- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Nov 2022 17:19:19 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[mediaqueries-5] Move the definition of "display mode" back to Manifest`. <details><summary>The full IRC log of that discussion</summary> <astearns> topic: [mediaqueries-5] Move the definition of "display mode" back to Manifest<br> <chris> s/???/F2F<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/7306<br> <dandclark> Erik: The motivation is the webapps wg will be writing definitions for more display modes. Makes sense for them to vote on modes and their positions.<br> <florian> q+<br> <dandclark> Erik: ???<br> <astearns> s/???/uncontroversial in webapps wg/<br> <dandclark> florian: There's editorial and substantive aspects to this. Substantive aspect is that while most dipslay modes are only invokable by app manifest, there's at least one that iIm not sure if should be. that's fullscreen.<br> <dandclark> florian: If you invoke UI to switch viewport to full screen, should this be recognized as full screen?<br> <dandclark> florian: When you're in full-screen mode, you're in full-screen mode regardless of how you got there. If you want full-screen mode to be stricly about the manifest, can do what was suggested.<br> <tantek> +1 I think I'm agreeing with florian, which is to keep the more abstract (non-manifest-specific) definitions in MQ5<br> <dandclark> florian: But if you want media queries to be generalized, we can move the bulk of what's here to the spec but might need to leave a bit behind in media queries.<br> <dandclark> Erik: Manifest might say fullscreen but you're not in that mode at the moment ??? This would be similar to standalone. I think uncontroversial that if you start in browser and go to fullscreen, it should go to fullscreen. Don't think there's a problem. Distinction between what manifest says and what the browser's doing.<br> <dandclark> florian: Two nuances, we agree on first but not sure on second. If you have manifest but mode isn't active, what counts is what's actually active. If you don't have manifest, and you put browser in full-screen, I think you're saying you agree full screen mode should apply . We agree. But PR to put it back to the webmanifest spec doesn't agree.<br> <dandclark> erikwilligers: We can quickly resolve htis afterward, test what the browsers do.<br> <dandclark> florian: Do we want to generalize this to be more applicable broadly?<br> <tantek> +1 worth generalizing<br> <dandclark> florian: IF we accept PR as is, applies to webmanifest only, but it's worth generalizing<br> <dandclark> erikwlligers: I don't see any problems<br> <dandclark> florian: We need some things in both specs. IF only need this to apply to webapp manifest, almost everythign should move there. ONly need cross-referencing.<br> <dandclark> florain: To apply more broadly, need some definition in media queries.<br> <dandclark> astearns: Do we resolve to accept PR now?<br> <dandclark> astearns: ...and then track remaining work in this issue or another? Or not accept PR yet?<br> <dandclark> erikwilligers: Resolve to have remainder here<br> <dandclark> florian: Not sure, e.g. definition of display-mode itself. If this notion is broadly applicable, not sure if should move.<br> <dandclark> rossen: This conversation suggests this isn't ready to merge. Close but not quite. Take this extra time with florian and come back when it's ready?<br> <dandclark> erikwilligers: I guess we can do that<br> <tantek> +1 Rossen. Iterate on the PR and re-review next week?<br> <dandclark> astears: Take the time to hammer it out and we'll take it up again<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7306#issuecomment-1317378222 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 November 2022 17:19:20 UTC