- From: Ultinio via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Oct 2024 19:38:59 +0000
- To: public-css-archive@w3.org
Alright, I didn't have an opinion about one or the other (part of grid or its own display type), but let's admit plenty of developers are confused when they have to choose between grid or flex. So it's already not really clear. As @essenmitsosse wrote, it might be a step in the wrong direction. Instead of making things even more confusing for developers, why not giving them the possibility to define ways to fill a container in a more general way ? Not mentioning Javascript or the solutions adding some JS-or-similar-system into CSS because it shouldn't be like that and this whole conversation is actually to avoid JS in the first place. But if there is no possibility to change the whole system in the short term, here it feels like grid-auto-flow is the property designed to tell the browser where and how to add new elements. Isn't it why this property is there ? To know where to add new elements ? So it could be added to grid-auto-flow, as masonry or waterfall (whatever). Columns are defined as usual with grid-template-rows, and the algorithm knows what to do with new elements. Or maybe I am wrong and please feel free to show me some examples where this cannot work. -- GitHub Notification of comment by Ultinio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2400678040 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 October 2024 19:39:01 UTC