- From: Sebastian Zartner via GitHub <noreply@w3.org>
- Date: Fri, 23 Jan 2026 22:16:34 +0000
- To: public-css-archive@w3.org
@bfgeek: > Breaking this convenience for spec purity is a large disservice to web developers. It costs browser engines nothing[1] to add this feature, and doesn't harm CSS as a language going forward. This is not at all about spec purity. It is about educating authors that there is a two-value syntax. And the two-value syntax is still quite new, while the single-value keywords are around for much longer. So, of course, the adoption is still much lower. And that low adoption rate is also the reason why LLMs still suggest the single-keyword values. @jensimmons: > Just making `display: inline-grid-lanes` invalid is only going to confuse people. It's going to make them think Grid Lanes doesn't work as an inline container. That it has to be block. I'd say it is more likely that they look it up and check why `inline-grid-lanes` is not working and find those articles that explain the two-value syntax. Or they ask their favorite LLM that tells them so. And teaching resources and articles aside, an auto-completion of multiple keywords in tools would probably already go a long way. Furthermore, once we turn `display` into a shorthand for inner and outer display values (see #4729 and related ones), the two-value syntax will surely see a huge increase in adoption. Single-value vs. two-value syntax aside, I agree with @kizu who noted that there probably aren't that many use cases for an inline grid-lanes layout, anyway. And as he noted, "if you actually need inline grid-lanes, you probably know a lot about how display works". Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3792796927 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 January 2026 22:16:35 UTC