- From: bravecrayon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 14:25:12 +0000
- To: public-css-archive@w3.org
I prefer the idea of leveraging the existing grid syntax and properties. Masonry seems to be an _extension_ of grid. Grid is a good, generic concept for creating many specific layouts, of which masonry is but one endpoint. Masonry is a tweak or modification; a _style_ of grid. Elevating a specific way of displaying boxes on a grid to a whole new `display` value, while adding new properties/syntax to support that, seems cumbersome. You'd really need a good case for why to do that. There exists already, in my opinion, too many different ways with difficult-to-remember syntax and keywords to flow content. I can very easily imagine myself starting with "grid" layout at the onset of a project and needing to switch to masonry style later. I would need to rewrite a bunch of CSS if it was its own `display` value with specific supporting properties. On the second point of what to call it if it was a keyword for `grid-template-*`, using "collapse" is ok, but I'd prefer something like "pack" or "packed", as in "packed tightly", because I think it's more memorable for my visual brain. I suppose "stacked" could also work, but doesn't work well for the horizontal axis. Also, I have already associated "collapse" with `border-collapse`, which would mean the same keyword means two different concepts/effects based on context, so naming it something more unique like "packed" is preferable. -- GitHub Notification of comment by bravecrayon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11060#issuecomment-2432396618 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 14:25:12 UTC