307255 2026-02-07 17:44:10 -0800 Remove `display: inline-grid-lanes` if CSSWG changes resolution again 2026-02-09 12:22:34 -0800 1 1 1 Unclassified WebKit CSS WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 1 obrufau webkit-unassigned ahmad.saleem792 brandonstewart fantasai.bugs jensimmons koivisto webkit-bug-importer oldest_to_newest 2179124 0 obrufau 2026-02-07 17:44:10 -0800 See https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3720021476 > RESOLVED: remove inline-grid-lanes for now, but we are open to adding it again if there is evidence it solves a problem Note another resolution (https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3820508516) reverted the former, but the latter got a formal objection (https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3829784658). So the former resolution stands: the `display: inline-grid-lanes` should be removed, in favor of `display: inline grid-lanes`. 2179234 1 webkit-bug-importer 2026-02-08 14:43:26 -0800 <rdar://problem/169929742> 2179240 2 ntim 2026-02-08 14:52:41 -0800 Removing parsing support is easy, the harder part to keep round-tripping and serialization sane. WebKit can't serialize `display` to multiple values with the current setup. It's not terribly hard to make that supported, but it is more than just removing the value. 2179252 3 obrufau 2026-02-08 15:19:13 -0800 Maybe it helps for reference, https://chromium-review.googlesource.com/c/chromium/src/+/2421598 is the patch that added `block math` in Blink, its first display value that can't be expressed as a single keyword. 2179538 4 jensimmons 2026-02-09 12:22:34 -0800 Currently, the CSSWG has resolved to keep `display: inline-grid-lanes`. https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3820508516 There are still people who believe this is the wrong decision, so the debate will likely continue.