- From: Benjamin den Boer via GitHub <noreply@w3.org>
- Date: Mon, 25 Aug 2025 08:22:09 +0000
- To: public-css-archive@w3.org
To add to @franciscolourenco’s point, visual and text editors often will want to use `white-space: pre-wrap` or `white-space: pre` to let designers use spaces to control the flow of text for cases where `text-align` does not suffice. (The exact value used depends on the `width` value of the text layer). Without it, pressing `space` while writing copy would not do anything. As you can imagine, this would instantly feel broken. <img width="612" height="313" alt="Image" src="https://github.com/user-attachments/assets/30798b8c-ad14-4769-93ae-8840a46f1d2f" /> --- Similarly, designers and content editors often will then use truncation (`line-clamp`) for dynamic content, and its ability to design layouts with fixed amounts of lines, but the combination leads to the redundant space just before the ellipses, which is rarely what you want when visualizing truncation. <img width="1014" height="501" alt="Image" src="https://github.com/user-attachments/assets/533e203e-7bd4-46c5-a1ea-518694fed67f" /> --- Unlocking the combination of `pre-wrap` and `pre` with proper truncation means a lot to visual editors with freeform canvases, as well as rich text editing tools, unlocking great UX for web editors that meets expectations of creatives. -- GitHub Notification of comment by benjamindenboer Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12008#issuecomment-3219298198 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 August 2025 08:22:10 UTC