- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Mon, 05 Jan 2026 22:44:54 +0000
- To: public-css-archive@w3.org
I mentioned this in the call but wanted to add this point to this issue, as well, to make sure it is properly tracked. For the proposal of `grid: [ rows | columns ] <track-listing> || <string>+ || <'grid-auto-flow'>;`, one major downside is that one part of the shorthand could override another part of the shorthand in the same declaration. I'm not sure there is precendence for this, and it seems like a fairly strange side effect. More explicitly, if an author sets `grid: rows 100px 100px row-reverse` you'd end up with column tracks instead of rows (even though the author specified `rows` at the beginning of the statement) because `row-reverse`, per this proposal, would be a column layout. As such, `grid-auto-flow`, if specified by the author in the shorthand, always wins, no matter what `[rows | columns]` is set at the beginning. Even though this is a separate issue from https://github.com/w3c/csswg-drafts/issues/12803#issuecomment-3664178603, this side effect is another major reason why I believe we should be adding separate properties for grid-lanes in both issues so that we can create properties that are easier to reason and makes sense within the single axis layout model of grid lanes. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12023#issuecomment-3712342984 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 January 2026 22:44:55 UTC