Re: [csswg-drafts] [css-grid-3] Renaming `masonry` keyword (#9733)

> this really isn’t about the layout used by Pinterest or other similar sites. This is a mechanism for telling the browser, “please create a grid, but without any rows.”

I was dubious about how masonry was even conceptually a kind of grid, but this [quote](https://webkit.org/blog/15269/help-us-invent-masonry-layouts-for-css-grid-level-3/) from the article on webkit was useful in seeing the gridness of it. So:

`grid-template-rows: no-rows`

Very explicit, no ambiguity or metaphor which might feel complex internationally, and no associations with what a masonry layout is 'for'. It's some kind of grid, but you turn the rows off. It's also less ambiguous than `off` or `none` (what is being turned off? of what is there none?), and it also resolves some of the discomfort around grid for me. 'a grid, with no rows'

The idea of using `no-align` because rows are in fact created is a good point, but just in terms of what feels intuitive to me, what I would expect to happen when I choose `no-rows` would look like masonry. `no-align`, I associate align with text-align and align-items, moving objects around in a space. By implication, `no-align` suggests there should be a value `align`, but there's not - the opposite is rules for rows, which aren't exactly alignment IMO. The pair 'rows like this' and 'no rows' feel more clear.

(`no-snap`? rows are present between objects, but objects don't snap to them - instead, the rows follow where the objects are. I like this less.)

There's also the way that align is used of vertical orientations in various contexts. Hopefully, masonry will be available for both rows and columns. It's a bit messy the way the orientation 'align' targets changes depending on how you're flexing. `no-rows` and `no-columns` are a clear pair, where 'align' makes me think 'aligning to what and in which direction'?

-- 
GitHub Notification of comment by TarryDan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9733#issuecomment-2068027875 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 21 April 2024 12:33:04 UTC