- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Wed, 11 Feb 2026 16:25:07 +0000
- To: public-css-archive@w3.org
Yes, we can (and often should) break precedent in favor of something better, when the old style was bad for whatever reason. That's not the case here. The difference is literally whether we spell the value with a space or a dash, and the proposal is that we continue to allow both, following existing precedent. The `inline-grid` precedent, *specifically*, is a strong consistency argument for having `inline-grid-lanes` as well. And it is of course important to remember that the argument is not "do we have dashed keywords, or spaced keywords". It's just "do we (continue to) have dashed keywords" - the space-separated syntax is already there and stable, with nobody suggesting any action around it. Whatever arguments one might have for why the space-separated syntax is *superior* are irrelevant for this argument, unless one is trying to make the (imo much more difficult to support) argument that having both forms is *confusing* or otherwise *harmful* to authors in some way. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3885516522 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 February 2026 16:25:08 UTC