- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 29 Jan 2026 21:59:20 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-grid-3] Should grid-lanes live in the Grid spec, or its own module?`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> q+<br> <sgill> astearns: should this live in grid 3 or its own? i lean towards latter<br> <sgill> jensimmons: why? what's the problem with where it has been?<br> <sgill> alisonmaher: precedence that it has happened before<br> <astearns> ack TabAtkins<br> <sgill> TabAtkins: also support moving it<br> <sgill> when you look at how huge grid 2 is, it would make it a huge spec to look at<br> <hober> q+<br> <sgill> would be harder to understand and reason through as a single spec<br> <sgill> there would be a lot of referencing but we already do that<br> <oriol> +1 to different spec<br> <dholbert> q+<br> <astearns> ack hober<br> <sgill> hober: what we put in modules is an editorial question<br> <sgill> as general rule of thumb i'm fine to defer to editor<br> <sgill> i suspect it would be less painful to keep it together but that is my guess<br> <sgill> TabAtkins: as editor that is why i want to separate it<br> <astearns> ack dholbert<br> <sgill> dholbert: don't have too strong an opinion<br> <TabAtkins> even with the GIANT TEXT things to help organize the Sublime visual menu, it's already hard to navigate Grid 2, lol<br> <sgill> one reason to keep it is that subgrid is one thing that shares tracks. masonry is one thing that shares tracks with things they are thrown into<br> <sgill> two different things that can participate with the grid<br> <florian> q+<br> <sgill> little bit of an exception with the new display type<br> <TabAtkins> subgrid is *mostly* limited to its one subsection, fwiw, with minimal interaction in the rest of the spec<br> <sgill> if it's editorially easier don't care too much<br> <astearns> ack fantasai<br> <sgill> fantasai: as another editor, i agree w/ Tab that it is getting long<br> <sgill> as we add more features to grid we will add it to both modes<br> <sgill> unlike other cases we have a core syntax that is connected between the two<br> <sgill> yes we could split it out. bunch of text that is in there is text already in grid 2 and that is not ideal either<br> <astearns> q+<br> <sgill> if we put it in the same module we can factor out into an upfront definition of thing. for grid you would do this and for grid lanes you would do that<br> <sgill> we can have one spec fully integrated<br> <hober> q+<br> <sgill> we can structure prose in a way that makes sense<br> <hober> q-<br> <sgill> one part that is hard is core part of layout algorithm. relatively short section<br> <sgill> biggest part of it is track sizing and is shared between the two<br> <sgill> not convinced we need to split it out<br> <sgill> once we integrate full text it will be better than having the separate incomplete module<br> <astearns> ack florian<br> <sgill> florian: generally agree that this is largely editorial but it is also looking forward<br> <sgill> depends on what we expect to happen next? in grid 4?<br> <sgill> would we add things that apply to both and add in grid 4? or only add things that only connect to grid lanes? or only to normal grid?<br> <sgill> maybe we would need a grid lanes level 2<br> <sgill> but if things are going to be shared maybe keep it together<br> <sgill> fantasai: we have a bunch of resolved things that are shared<br> <sgill> florian: indicates to me they should be together<br> <astearns> ack astearns<br> <sgill> fantasai: before we do anything else i want to get everything integrated together<br> <sgill> astearns: integration first seems like a crucial step<br> <ChrisL> q+ to mention css-color-hdr being separate from css-color<br> <miriam> +1 to starting integrated<br> <sgill> let's not split it out until that happens<br> <sgill> fantasai: definitely need to figure it out<br> <ChrisL> q-<br> <sgill> astearns: worried we might find corner cases we didn't consider. might be a good thing<br> <sgill> TabAtkins: run into those even with alignment. but the separation is worthwhile because of the conceptual boundaries<br> <sgill> PROPOSAL: Integrate the diff spec with grid<br> <fantasai> s/grid/grid L2/<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13115#issuecomment-3820644949 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 January 2026 21:59:21 UTC