Bug 307255 – Remove `display: inline-grid-lanes` if CSSWG changes resolution again

• Status: NEW
• Component: CSS

[Oriol Brufau]

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`.

[Radar WebKit Bug Importer]

<rdar://problem/169929742>

[Tim Nguyen (:ntim)]

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.

[Oriol Brufau]

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.

[Jen Simmons]

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.