- From: jfkthame via GitHub <noreply@w3.org>
- Date: Tue, 28 Oct 2025 13:05:58 +0000
- To: public-css-archive@w3.org
While I'm pretty comfortable with the `masonry` term here, I've recently come to think that actually `lanes` (or my preferred variation, `tracks`) is actually better. Consider the case where the grid tracks we're going to fill "in masonry style" run horizontally, so it's the case that looks most analogous to typical brick/stonework in the real world. How does a mason build a wall? In general, they lay one course of blocks at a time, building upwards and ensuring that the joints in successive rows are staggered. They don't usually build the wall to its full height at one end and then keep extending it sideways. The end result once the wall is complete (the layout is filled to its available space) looks similar to what we're discussing here. But the process of getting there -- the sequence in which blocks are placed into the wall -- is quite different: a mason fills the lowest row, then lays another row on top of it, etc., whereas this layout mode starts filling _all_ the rows from one end, packing blocks into whichever is shortest at the time. So the expected ordering of the items is quite different. Picture vehicles arriving along a highway to a toll plaza with 20 lanes: each arriving driver will aim for whichever lane currently looks like it has the shortest queue. That's how this layout mode fills items into the lanes; _not_ like how a mason builds a wall, course (lane) by course. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12022#issuecomment-3456381060 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 October 2025 13:05:59 UTC