- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Feb 2018 17:38:47 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `[mediaqueries] How do media queries with calc() where it can be resolved early serialize?`, and agreed to the following resolutions: * `RESOLVED: Have calc serialize in MQ same as properties, have that called out in the spec, and then test to see if we can follow that.` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [mediaqueries] How do media queries with calc() where it can be resolved early serialize?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1968<br> <dael> florian: A few weeks back we decided that calc is supposed to simplify down as soon as it can, but not simplify away.<br> <dael> florian: Raised against MQ. Impl were new, but 2 new impl we not doing that. Chrome was about to agree to not do that which means remove the calc when serializing. In same discussion it was raised if combining length units early was if we wanted.<br> <dael> florian: I don't have a stand, but since impl sort of disagree on the resolution we need to revisit. I think TabAtkins thought what w resolved was good.<br> <dael> TabAtkins: I'm not strong either side. Whatever works.<br> <dael> florian: Do we have anyone who wanted to impl the other thing?<br> <dael> astearns: Not enough strong opinions on the call.<br> <dael> astearns: Reading dbaron comment it sounds like you'd be against dropping calc?<br> <dael> dbaron: I'm catching up on the issue<br> <dael> dbaron: I was pointing out one issue wiht dropping calc it sometimes makes a thing valid that wouldn't be valid without the calc. We don't check range restrictions in calc<br> <dael> florian: IN FF and webkit that's what they do. If you have aspect ratio of -1/-1 with a calc it serialized through as all which is what you'd expect.<br> <dael> dbaron: Maybe...I don't know how well calc validity rules are spec. Changing validity rule would need to be spec carefully<br> <dael> florian: In same discussion MQ in em serializes to em but em+px serializes to px in a calc and why.<br> <dael> florian: Do we need to revisit how calc seralizes in MQ? Happy with existing rules? Revist based on impl?<br> <dael> florian: Asking differently: when we resolved on rules for calc in general context were people in favor of what we resolved remembering MQ or did we forget and need to investigate?<br> <dael> astearns: I do not recall MQ being part of that convo<br> <dael> fremy: I don't see a point of making them different. We don't support calc but if we did it would be same as properties. If no one is arguing different we should stick with what we have.<br> <dael> florian: Yep. It was pointed out all impl don't do that but it could be a bug. There isn't a problem of web compat because this is new. But if we resolve one thing in spec and everyone impl something else it's not helping.<br> <dael> florian: IN other words, I'm happy to close won't fix and I'm happy to take tests from fremy and then file bugs one people. Deal?<br> <dael> fremy: Why not ^-^<br> <dael> astearns: Proposal is close, have clamping in MQ calc be exactly the same as for property values. We'll then have tests to see what's been impl and see if it matches reality?<br> <dael> florian: Informal tests say they don't, but formal let's us file bugs.<br> <dael> astearns: I like not having something special for MQ. But I think it's useful to have something explicitly discuss this in MQ spec so we can hang a test off it.<br> <dael> florian: Sure...<br> <dael> florian: I'll phrase it to explicitly refer to the cannonical text. Sounds good.<br> <dael> astearns: Proposal is have calc serialize in MQ same as properties, have that called out in the spec, and then test to see if we can follow that.<br> <dael> astearns: Obj?<br> <dael> REOSLVED: Have calc serialize in MQ same as properties, have that called out in the spec, and then test to see if we can follow that.<br> <dael> RESOLVED: Have calc serialize in MQ same as properties, have that called out in the spec, and then test to see if we can follow that.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1968#issuecomment-365685909 using your GitHub account
Received on Wednesday, 14 February 2018 17:39:26 UTC