- From: r12a via GitHub <noreply@w3.org>
- Date: Fri, 10 Apr 2026 07:32:58 +0000
- To: public-css-archive@w3.org
> If we don't really care about that, I think I'd agree that trim-both is enough, and that we could remove trim-start. Except that trim-start is supported by Blink, but trim-both is not (see https://w3c.github.io/i18n-drafts/articles/styling/inline-space.en.html#punc_initial_nospace — early draft !). That means we'd lose part of the little behaviour that currently works. :( But i have to say with the clustering of behaviour around these keywords, rather than having separate properties for paragraph-initial, line-initial, line-final, and punctuation-sequences is really hard for content authors to get their heads around the differences and which to use. Plus, i got the impression that there may be gaps, eg. for Traditional Chinese behaviour, that are not covered. I'm inclined to raise an issue to propose splitting them apart. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13779#issuecomment-4221957257 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 07:32:59 UTC