- From: Fuqiao Xue via GitHub <noreply@w3.org>
- Date: Thu, 09 Apr 2026 02:17:23 +0000
- To: public-css-archive@w3.org
xfq has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-text] `trim-both` and `trim-start` == https://drafts.csswg.org/css-text-4/#text-spacing-trim-property Recently, while discussing `text-spacing-trim` in CSS, the clreq TF felt that `trim-both` and `trim-start` are quite similar. The behavior of `trim-start` in certain cases appears to be counter-intuitive. For instance, if there isn't enough space remaining at the end of a line, the content might be pushed to the next line. This could trigger a line-breaking rule (such as preventing a closing quotation mark from appearing at the start of a line). And there is a high probability that three full-width characters would be pulled down to the next line (since a paragraph ending with a closing quotation mark typically includes a sentence-ending punctuation mark immediately preceding the quotation mark). Is there any specific scenario where `trim-start` is absolutely essential? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 April 2026 02:17:24 UTC