Re: [csswg-drafts] [css-grid] Growth limits not increased with min-content contributions of spanning items (#4790)

The CSS Working Group just discussed `Growth limits not increased with min-content contributions of spanning items`.

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Growth limits not increased with min-content contributions of spanning items<br>
&lt;AmeliaBR> github: https://github.com/w3c/csswg-drafts/issues/4790#issuecomment-664068575<br>
&lt;fantasai> https://drafts.csswg.org/css-grid-1/#algo-content<br>
&lt;AmeliaBR> fantasai: This will make more sense if I pull up the relevant section of the spec. ↑<br>
&lt;AmeliaBR> ... There are several sections in how we handle intrinsic sizes. Minimums first, then maximums. For minimums, there's auto and minimum/maximum. For maximums, there's no auto.<br>
&lt;AmeliaBR> ... When we edited the spec recently to add new terminology, we accidentally said “minimum” when we meant “min-content”. But when we went to fix that, discovered someone had implemented as written, so need to confirm the reversion.<br>
&lt;AmeliaBR> ... The current text is rather non-sensical. It's very rare/weird that min-content would be specified as the maximum value of your minmax range. We should fix it.<br>
&lt;AmeliaBR> astearns: Anyone have actual web compat information measured? Or should we change &amp; see if we get negative feedback.<br>
&lt;AmeliaBR> oriol: I do know there is no WPT for the bad behavior, although there is a Chromium internal test.<br>
&lt;fremy> sounds unexpected to me<br>
&lt;AmeliaBR> fantasai: I can't see any reason why anyone would write this code, with min-content in the max side of a minmax function.<br>
&lt;AmeliaBR> fremy: I don't expect people would do that. We should be able to fix this.<br>
&lt;AmeliaBR> PROPOSAL: Accept the edits made to the ED re minimum vs min-content (and add WPT tests)<br>
</details>


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

Received on Monday, 27 July 2020 20:48:10 UTC