Re: [csswg-drafts] [media-queries][css-sizing] Support <number> (and therefore calc) as a <ratio> (#3757)

The CSS Working Group just discussed `Support <number> (and therefore calc) as a <ratio>`, and agreed to the following:

* `RESOLVED: Accept proposal in favor of serializing with the calc expression`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Support &lt;number> (and therefore calc) as a &lt;ratio><br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3757<br>
&lt;dael> AmeliaBR: Finishing a discussion that was time clamp in Aug. Issue is about serialization issues.<br>
&lt;dael> AmeliaBR: Aspect ratio is unique and this applies to MQ and property- defined where division is part of syntax not jsut part of calc. Brought questions on how to serialize<br>
&lt;dael> AmeliaBR: Proposal I had was we trat numerator and denominator as sep/ components of the value. Each simplified as independent. If one is omitted the other becomes a default 1<br>
&lt;dael> AmeliaBR: Only issue I found since last discussion is right now both values required to be positive. Calc expressions that resolve to -value/-value you clamp them so it's 0/0 instead of negatives canceling. Might be worth doing clamping at used value as this is non-intuitive<br>
&lt;dael> TabAtkins: Allowing individual numbers to be calcs is consiquence to CSS syntax. All numbers can be calcs<br>
&lt;dael> TabAtkins: Agree negatives not worth allowing. I don't see why two negatives should pop out. Even if they would cancel doesn't seem worthwhile.<br>
&lt;dael> TabAtkins: Anything with single calc?<br>
&lt;dael> AmeliaBR: Single calc is same as single number. I prop for serialization that's your numerator and insert the missing denominator as a 1<br>
&lt;dael> jen: Agree but don't see practical case for negative over negative so if that's difficult I'm for disallowing<br>
&lt;dael> AmeliaBR: Proposal as in my comment for Aug 28: Always serialalie as number/number where the numbers might be calc expressions<br>
&lt;dael> heycam: Against principle of shortest simplification, but fine for me. As long as we write that in spec<br>
&lt;dael> fantasai: Is shortest most backwards compat serialization<br>
&lt;dael> heycam: Is it a thing with this prop?<br>
&lt;dael> AmeliaBR: Yes with the MQ. Keep prop consistent with MQ<br>
&lt;fantasai> regardless, should indeed be made explicit :)<br>
&lt;dael> smfr: What about proposal to use units?<br>
&lt;dael> AmeliaBR: Agreed not to do that, but can do it by putting it inside a calc<br>
&lt;dael> smfr: Okay<br>
&lt;dael> Rossen_: Other comments? It's not perfect but sounds like best we can do<br>
&lt;dael> Rossen_: Objections to resolve in favor of serializing with the calc expression?<br>
&lt;dael> RESOLVED: Accept proposal in favor of serializing with the calc expression<br>
&lt;AmeliaBR> (that should really be "with the division", not a `calc()`!)<br>
</details>


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

Received on Wednesday, 2 October 2019 23:24:55 UTC