- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Feb 2020 11:22:14 +0000
- To: public-css-archive@w3.org
I spoke too fast, that alone won't solve problem 2 because `auto` as a max-track sizing function means `max-content`. So even if we make the minimum contribution be 0, we would distribute the max-content contribution into the growth limit. And [§11.6. Maximize Tracks](https://drafts.csswg.org/css-grid/#algo-grow-tracks) happens before [§11.7. Expand Flexible Tracks](https://drafts.csswg.org/css-grid/#algo-flex-tracks), so we would get the same result. Maybe the change from #3705 should be reverted, i.e. if an item spans some flex track, only distribute its intrinsic contribution among flex tracks. And if no flex track is intrinsic, so be it, no contribution will be distributed. This used to be a bit problematic because could mean that the automatic minimum size could force an item to become bigger than its grid area. But this should be fine if the automatic minimum size becomes 0 when the item spans some flex track. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-587413703 using your GitHub account
Received on Tuesday, 18 February 2020 11:22:15 UTC