Re: [csswg-drafts] [css-grid-3] Masonry Switch Syntax (#12022)

The CSS Working Group just discussed `[css-grid-3] Masonry Switch Syntax`, and agreed to the following:

* `RESOLVED: masonry switch will be display: grid-lanes`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> fantasai: survey had over 300 responses<br>
&lt;kbabbitt> ... popular ones are listed in issue<br>
&lt;kbabbitt> ... top choices include grid-stack, packed-grid stuff<br>
&lt;kbabbitt> ... also grid-lanes or lane-grid<br>
&lt;kbabbitt> ... if you merge some options together that was among the top<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/12022#issuecomment-3488350977<br>
&lt;kbabbitt> ... ^ link to top options<br>
&lt;kbabbitt> ... concerns about stack because of confusion with stacking context<br>
&lt;kbabbitt> ... people thought pack got confused with density<br>
&lt;kbabbitt> ... looking at results, TabAtkins alisonmaher and I concluded grid-lanes seemed popular and didn't have downsites<br>
&lt;kbabbitt> ... also works well for creating a shorthand for this purpose<br>
&lt;alisonmaher> q+<br>
&lt;kbabbitt> ... that's currently what we're thinking is best among surveyed options<br>
&lt;ydaniv> q+<br>
&lt;astearns> ack alisonmaher<br>
&lt;kbabbitt> alisonmaher: comment on one of those options<br>
&lt;miriam> as my own personal top vote, I approve :)<br>
&lt;kbabbitt> ... do others have ideas on final 2?<br>
&lt;kbabbitt> ... I'm not opposed to grid-lanes, but one downside I see is we have concept of tracks<br>
&lt;oriol> q+<br>
&lt;kbabbitt> ... if we introduce term for lanes, we'd have both that and tracks, could be confusing<br>
&lt;kbabbitt> fantasai: we don't expose tracks anywhere, just a spec internal term<br>
&lt;astearns> ack ydaniv<br>
&lt;kbabbitt> ydaniv: what about just lanes?<br>
&lt;kbabbitt> astearns; we already resolved to have grid in value nam,e<br>
&lt;kbabbitt> TabAtkins: otherwise I'd agree<br>
&lt;astearns> ack ydaniv<br>
&lt;astearns> ack oriol<br>
&lt;kbabbitt> oriol: fantasai was saying it would work well with shorthand, can you clarify?<br>
&lt;kbabbitt> fantasai: Google proposed a sghorthand tailored to masonry that sets only one axis of grid values<br>
&lt;kbabbitt> ... they were calling that shorthandmasonry<br>
&lt;kbabbitt> ... can't use that but grid-lanes would still work for that purpose<br>
&lt;kbabbitt> astearns: am I correct that the quick part of this is poll between grid-lanes vs masonry-grid as the display value?<br>
&lt;kbabbitt> q+<br>
&lt;TabAtkins> grid-lanes: column repeat(3, auto);<br>
&lt;fantasai> scribe+<br>
&lt;astearns> ack kbabbitt<br>
&lt;TabAtkins> kbabbitt: one thing I discovered<br>
&lt;TabAtkins> kbabbitt: in terms of what people are referring to this with...<br>
&lt;TabAtkins> kbabbitt: "masonry" has been in use since 2009<br>
&lt;fantasai> kbabbitt: In terms of referring, name of masonry has been in use since 2009, so this is what authors have been calling it for a long time<br>
&lt;TabAtkins> kbabbitt: authors have been using the term for a very long time<br>
&lt;fantasai> kbabbitt: Not objecting, but still preference for grid-masonry<br>
&lt;kbabbitt> POLL: 1. grid-lanes, 2. masonry-grid<br>
&lt;miriam> 1<br>
&lt;fantasai> 1<br>
&lt;alisonmaher> 2<br>
&lt;oriol> 2<br>
&lt;bts> 1<br>
&lt;kbabbitt> 2<br>
&lt;florian> 1<br>
&lt;ntim> 1<br>
&lt;kizu> 1<br>
&lt;iank_> 2<br>
&lt;ydaniv> 1<br>
&lt;ChrisL> 1<br>
&lt;adamargyle> 1<br>
&lt;rachelandrew> 2<br>
&lt;astearns> 2<br>
&lt;dholbert_> 1 (but am flexible)<br>
&lt;Snugug> 2<br>
&lt;TabAtkins> no pref<br>
&lt;schenney> 1<br>
&lt;flackr> 1 or 2<br>
&lt;saku> 1<br>
&lt;kzms2> 1<br>
&lt;emilio> 1<br>
&lt;kbabbitt> astearns: seeing a 3:2 advantage for grid-lanes, not conclusive but better than we've had up till now<br>
&lt;TabAtkins> yeah, 14 to 8 or so<br>
&lt;TabAtkins> about a 3:2<br>
&lt;kbabbitt> astearns: Proposed: masonry switch will be display: grid-lanes<br>
&lt;kbabbitt> RESOLVED: masonry switch will be display: grid-lanes<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12022#issuecomment-3525043825 using your GitHub account


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

Received on Thursday, 13 November 2025 03:18:34 UTC