- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Sep 2023 20:26:08 +0000
- To: public-css-archive@w3.org
> Masonry's entire reason for existing is to allow you to place items according to the tracks' current fill height I'd argue that this is not true. The spec's introduction says this: > This module defines a layout system that removes that restriction so that items can be placed into Grid-like tracks in just one of the axes, while stacking them one after another in the other axis. _This_ is the main use case for Masonry. The auto-placement algorithm is _one_ aspect of it, like it is for Grid layout. And restricting it to auto-placement seems arbitrary to me and is also hugely restricting its usefulness. Allowing to place items manually (in addition to auto-placement) opens Masonry up to a whole new class of use cases. The use case is _not_ "flow multiple items into one grid cell". (That's handily expressed so that it fits to #9098.) The use case is "have multiple tracks in one axis and stack items in the other axis". Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-1712185019 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 September 2023 20:26:10 UTC