- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Sep 2023 23:14:59 +0000
- To: public-css-archive@w3.org
> They're not selecting the column based on available space; the stuff in the first column is _meant_ for the first column, the stuff in the second is _meant_ for the second. Right. That use case avoids the auto-placement algorithm altogether, like it can be done in Grid and Flexbox, already. The benefit over Grid is that they are only aligned on one axis and the benefit over Flexbox is that they don't rely on wrapping logic. > Today this would just be a grid with two columns and one row, with all the stuff in each column wrapped in a container. Correct. That's how it's solved right now in the first example. > To fix the general problem of wanting to flow a mixed set of contents into a single grid cell without having to pre-wrap them in a container div we have #9098 Yes, that issues would also solve that use case. Though that use case seems to be a natural fit for masonry and less so for grid. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1710875839 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 September 2023 23:15:02 UTC