- From: fantasai via GitHub <noreply@w3.org>
- Date: Fri, 10 Apr 2026 18:25:40 +0000
- To: public-css-archive@w3.org
This is an earlier syntax , which allowed splitting up these controls: https://www.w3.org/TR/2022/WD-css-text-4-20221231/#text-spacing-property ``` normal | [ trim-start | space-start | space-first ] || [ trim-end | space-end | allow-end ] || [ trim-adjacent | space-adjacent ] ``` The syntax space was simplified in https://github.com/w3c/csswg-drafts/issues/4246 (see the [changes list in the following WD](https://www.w3.org/TR/2023/WD-css-text-4-20230301/#changes) for notes on other related changes), which (with the later addition of `trim-all`), cut it down to ``` space-all | trim-auto | [ allow-end || space-first ] | trim-all ``` The discussion in https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1853187016 added `normal` and flattened the syntax to what it is now (with https://github.com/w3c/csswg-drafts/issues/10161 renaming `trim-auto` to `trim-both`: ``` normal | space-all | space-first | trim-start | trim-both | trim-all ``` And that's how we got to where we are today. We _could_ expand it back out (the existing syntax is just a subset of the full set), but the question is, should we? -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13789#issuecomment-4225871685 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 April 2026 18:25:41 UTC