- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 17 Sep 2025 15:25:56 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow] [css-text] Interaction between whitespace collapsing and line-clamp`, and agreed to the following: * `RESOLVED: Rendering should be equivalent to line breaking at that soft wrap opportunity, and applying white space processing part 2 before inserting ellipsis at the end` <details><summary>The full IRC log of that discussion</summary> <fantasai> i/florian: there seems to be/scribenick: ydaniv<br> <fantasai> scribe+<br> <fantasai> andreubotella: Block finds the last soft wrap opportunity and removes content from that point to end of line<br> <fantasai> andreubotella: What does that mean in terms of whitespace?<br> <fantasai> andreubotella: wrt unicode line breaking algo, line breaking opportunity is after the space, not before<br> <fantasai> andreubotella: This is probably not what we want<br> <fantasai> andreubotella: Way I conceptualize this is, rather than finding last opportunity that fits, remove the width of ellipsis from the available width of the line, do regular line breaking based on that, and then add the ellipsis<br> <fantasai> andreubotella: in that model, if the ellipsis is placed after white space processing part II, which removes collapsible spaces, it will be placed at the end of the word<br> <florian> q+<br> <fantasai> andreubotella: I don't necessarily want to require that the line-breaking algo has to take into account the ellispsis, that's an implementation strategy<br> <fantasai> andreubotella: proposed resolution, if you have clamp point at white space, make it work as if line break happened there, and ellipsis was placed after WS Processing Part 2<br> <astearns> ack florian<br> <fantasai> andreubotella: which removes the space<br> <fantasai> florian: I agree with the proposal<br> <fantasai> florian: Don't want to require a particular implementation strategy, but describing this way is helpful and easy because we invoke existing spec text<br> <fantasai> florian: that's a very complicated logic depending on which spaces and white space properties are at the end of the line<br> <fantasai> florian: so saying we do "as if" at the end of the line is a good idea<br> <fantasai> andreubotella: Another complication related to hanging white space<br> <fantasai> andreubotella: You can have space at the end of the line that isn't collapsible, but can hang off the end of the line (width isn't accounted for in line breaking or alignment)<br> <fantasai> andreubotella: Only space at the end of the line can hang. If you put ellipsis there, can't hang anymore.<br> <fantasai> andreubotella: We could make the ellipsis hang... so not impossible<br> <fantasai> andreubotella: but idk if we want to require that or what<br> <fantasai> astearns: Let's say that's a separate issue for now, and take a resolution on what we do with collapsible white space<br> <fantasai> andreubotella: "Rendering should be equivalent to line breaking at that soft wrap opportunity, and applying white space processing part 2 before inserting ellipsis at the end"<br> <fantasai> astearns: Makes sense<br> <fantasai> PROPOSED: Rendering should be equivalent to line breaking at that soft wrap opportunity, and applying white space processing part 2 before inserting ellipsis at the end<br> <fantasai> RESOLVED: Rendering should be equivalent to line breaking at that soft wrap opportunity, and applying white space processing part 2 before inserting ellipsis at the end<br> <fantasai> fantasai: fwiw, if we put ellipsis after the spaces, then nothing should hang anymore<br> <fantasai> florian: yeah, question is whether that's where the ellipsis should go<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12008#issuecomment-3303529103 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 September 2025 15:25:57 UTC