- From: Naman Goel via GitHub <sysbot+gh@w3.org>
- Date: Sun, 29 Sep 2024 19:43:30 +0000
- To: public-css-archive@w3.org
@cat394 Thank you for your explanation and with the current proposed design it makes a lot of sense. And just to further clarify my last comment, I completely understand not thinking of masonry as a grid but as a new type of layout. I was specifically warning against thinking about it like Flexbox too much. (@Loirooriol you essentially used "wrapping" to make masonry and not really the core feature of flexbox, which is to "flex" the children to grow or shrink, which was my entire point. But also, thanks for the great solution!) If the design of the proposal doesn't change, I think your argument holds up very well. I'm however unsure if we've landed on the right approach for masonry. This talk from Nicole Sullivan really brought up a lot of questions for me. https://www.youtube.com/watch?v=3h6BCTgQ4yw 1. As @cat394 mentioned, masonry doesn't just "float items up". Rather, the order of the items can change altogether. This is often an undesirable behaviour and for a clean tab-index order it's often best to minimize the amount of re-ordering that takes place and to maintain the left to right order of children when possible. 2. I also think it's very useful to be able to define `*-columns: 1fr min-content` to be able to make the layout useful 3. I also found the idea of mixing grid and masonry intriguing. I think it's worth considering layouts where certain columns ignore the row tracks and pack the children within them, but not others. Neither API proposal would currently support this. --- Traditionally, masonry on the web has been kind of pigeonholed into few use-cases. This is primarily because it wasn't a native CSS feature. When adding a new CSS layout, let's be careful about the widest possible number of use-cases. -- GitHub Notification of comment by nmn Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2381579128 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 29 September 2024 19:43:31 UTC