- From: fantasai via GitHub <noreply@w3.org>
- Date: Tue, 17 Feb 2026 22:15:03 +0000
- To: public-css-archive@w3.org
> it's a little silly to call them legacy if we're still adding them This. > In general, the CSSWG intends to support new display modes with the two value syntax only, This was our intention ten years ago, and ten years is a long time ago. If we're not willing to go along with that intention now, why does it make sense to keep that intention on the books? What makes us think that we would follow through on that intention in the future, if we aren't going to follow through on it now? > I'm not saying that much, but note that serialization prefers the legacy one, so adding both relegates the new (better) syntax as some kind of 2nd class citizen. Just wanted to highlight this point by @Loirooriol. It doesn't make sense to say in prose that the two-keyword syntax is preferable and the one-value syntax is discouraged while also continuing to add new hyphenated versions and making the OM auto-convert the two-keyword values to (supposedly legacy) hyphenated ones. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10961#issuecomment-3917351629 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 February 2026 22:15:04 UTC