Re: [csswg-drafts] [css-grid-3] Drop `masonry-auto-flow: definite-first`? (#10260)

The CSS Working Group just discussed ``[css-grid-3] Drop `masonry-auto-flow: definite-first`?``, and agreed to the following:

* `RESOLVED:  drop the definite-first value of masonry-auto-flow`

<details><summary>The full IRC log of that discussion</summary>
&lt;dbaron> ScribeNick: dbaron<br>
&lt;dbaron> TabAtkins: the spec doesn't currently define the masonry auto flow ? value<br>
&lt;dbaron> TabAtkins: can be inferred what it means<br>
&lt;dbaron> TabAtkins: distinction between items in a definite track versus items purely auto placed.  That value means that anything you place indefinite will go first and then all auto-placed ones below it.<br>
&lt;dbaron> TabAtkins: I think it's a bad behavior.<br>
&lt;dbaron> TabAtkins: intended to match with grid 's behavior but it doesn't.<br>
&lt;dbaron> TabAtkins: what grid does is it breaks items into 4 categories.<br>
&lt;dbaron> TabAtkins: things with definite row + column, a definite row (any column), a definite column (any row), and fully auto placed<br>
&lt;dbaron> TabAtkins: it handles these in order of strictness<br>
&lt;dbaron> TabAtkins: in order to minimize chance of overflow<br>
&lt;dbaron> TabAtkins: so first it places things that are fully definite (row + column)<br>
&lt;dbaron> TabAtkins: next it places anything with a definite row, since if the row gets filled up it will overflow the row<br>
&lt;dbaron> TabAtkins: finally it flows column placed things and auto-placed things together as one category in order<br>
&lt;dbaron> TabAtkins: this is because column-placed things, worst case, they get shifted to the next column (??), so almost as flexible as auto-placed<br>
&lt;dbaron> TabAtkins: masonry stuff is all the final two categories<br>
&lt;dbaron> TabAtkins: so I think the default behavior is to match grid and flow them all together<br>
&lt;dbaron> TabAtkins: I think there's no actual use case for definite first.<br>
&lt;dbaron> TabAtkins: if you want things first, use the order property.<br>
&lt;fantasai> dbaron: I think it makes sense<br>
&lt;dbaron> s/column (??)/row/<br>
&lt;dbaron> fantasai: any objections to dropping the definite-first value of masonry-auto-flow<br>
&lt;dbaron> RESOLVED:  drop the definite-first value of masonry-auto-flow<br>
</details>


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


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

Received on Wednesday, 12 June 2024 08:08:34 UTC