Re: [csswg-drafts] [css-sizing-3][css-grid-3][Masonry] Compressible Replaced Elements (#12563)

The CSS Working Group just discussed `[css-sizing-3][css-grid-3][Masonry] Compressible Replaced Elements`, and agreed to the following:

* `RESOLVED: When both the min and max sizes in a minmax() are indefinite, use the max (growth limit), consistent with what we do when we have two definite sizes.`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> fantasai: currently when you have an auto repeat we figure how many columns, and then do column sizing<br>
&lt;ydaniv> ... we need some sizing to use for repeatition<br>
&lt;ydaniv> ... so grid only allows fixed sizes or a mix of fixed and indifinite<br>
&lt;ydaniv> ... and we use the max<br>
&lt;ydaniv> ... if both min and max, we take the max<br>
&lt;ydaniv> ... for indifinite sizes there's a question whether to use the min or max one<br>
&lt;ydaniv> ... suggestion is to use the max when both are same type<br>
&lt;ydaniv> almaher: we did this in CH impl. and looks good<br>
&lt;ydaniv> astearns: other comments?<br>
&lt;fantasai> Proposal: When both the min and max sizes in a minmax() are indefinite, use the max (growth limit), consistent with what we do when we have two definite sizes.<br>
&lt;ydaniv> astearns: objections?<br>
&lt;ydaniv> RESOLVED: When both the min and max sizes in a minmax() are indefinite, use the max (growth limit), consistent with what we do when we have two definite sizes.<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 1 October 2025 15:40:33 UTC