- From: Romain Menke via GitHub <noreply@w3.org>
- Date: Tue, 10 Feb 2026 18:24:52 +0000
- To: public-css-archive@w3.org
> both users and guides overwhelmingly still favor the single-keyword version Up until very recently the multi-keyword syntax wasn't Baseline Widely Available and the docs actively warned against using the multi-keyword syntax as a result of that. I don't think we can make the assumption that users favor the `inline-*` syntax. I think they didn't consider it ready for production use. It takes a really long time before authors voluntarily switch to a syntax that has worse browser support, especially if it doesn't offer new capabilities. This however doesn't necessarily mean that they don't want to use the more modern syntax. I think we need to recognize that we can't get a clear signal from authors about what they favor at this point in time, purely by looking at past behavior. I am not saying that authors don't want `inline-grid-lanes`. I am sure that some authors will try the `-` and be surprised if it doesn't work. Personally I don't feel very strongly about adding or not adding `inline-grid-lanes`. Anecdotal evidence (from authors!) seems to indicate that it is fine to not add this but other than that I am fine with adding it. ------ Can we do a compromise? - add `inline-grid-lanes` - keep all the `inline-*` (including `inline-grid-lanes`) marked as legacy syntax - decide not to add `inline-*` variants in the future, with the option to revisit later When there is a new display mode in ±5 years we will have a much clearer view on what authors favor and how aware they are of the multi-keyword syntax. Marking these as legacy helps to promote the multi-keyword syntax in documentation, lint rules, ... If these are not marked as legacy it is much harder to drive adoption. Authors can learn about `inline grid-lanes` and thereby also discover the multi-keyword syntax. But those that just try `inline-grid-lanes` won't get surprises. (Keeping in mind that we are not considering a deprecation or removal of `inline-*`, only an indicator that this syntax is legacy.) -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3879948345 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 February 2026 18:24:53 UTC