Re: [csswg-drafts] [css-grid][css-flex] Indefiniteness when sizing grid tracks in a flexible flex item (#4852)

The CSS Working Group just discussed `Indefiniteness when sizing grid track inside flex item`, and agreed to the following:

* `RESOLVED: close no change, firefox is correct`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Indefiniteness when sizing grid track inside flex item<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/4852<br>
&lt;fantasai> oriol: Case where we don't have interop between FF and Chrome<br>
&lt;fantasai> oriol: When have column flex container which has for example height set to some value bigger than the content<br>
&lt;fantasai> oriol: This flex item has a flex that causes it to expand<br>
&lt;fantasai> oriol: and this flex item is also a grid container<br>
&lt;fantasai> oriol: which contains an auto row<br>
&lt;fantasai> oriol: usually auto rows, if you have free space at end of track sizing, they are expanded to cover this extra space<br>
&lt;fantasai> oriol: specifically for the case where we set the height property, we have interop<br>
&lt;fantasai> oriol: but instead of setting height on flex container you set min-height, in Chrome the auto height doesn't grow<br>
&lt;fantasai> oriol: At first I was confused and thought Chrome was right, but actually after some feedback from iank_ I think it's actually Firefox which follows the spec<br>
&lt;fantasai> oriol: iank_ also said that he's willing to change Chrome to adapt to what FF is doing<br>
&lt;fantasai> oriol: So I guess we can close this no change, agreeing that Firefox is the right behavior<br>
&lt;fantasai> Rossen_: comments/objections?<br>
&lt;fantasai> iank_: ...<br>
&lt;fantasai> fantasai: I think authors would be happy with this resolution<br>
&lt;fantasai> RESOLVED: close no change, firefox is correct<br>
</details>


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


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

Received on Wednesday, 21 July 2021 16:30:56 UTC