Re: [csswg-drafts] [css-overflow-4] nowrap and block-ellipsis (#12811)

The CSS Working Group just discussed `[css-overflow-4] nowrap and block-ellipsis`, and agreed to the following:

* `RESOLVED: clarify the interaction between nowrap and block elipssis`

<details><summary>The full IRC log of that discussion</summary>
&lt;ydaniv> florian: there seems to be some ambiguity about text spec<br>
&lt;ydaniv> ... when you remove content next to elipsiss it should disappear<br>
&lt;ydaniv> ... up to the next soft wrap oppertunity<br>
&lt;ydaniv> ... but the way the white space is currently specified, nowrap and pre do not supress it<br>
&lt;ydaniv> ... so reading it says that even if it says nowrap they do not suppress the wrapping oppertunity, just not to take them for line break processing<br>
&lt;ydaniv> ... so literal reading would have it do something else<br>
&lt;ydaniv> ... proposal is to not do that, and leave to the editor to find exact spec wording, and confirm that when you can't wrap you remove the whole thing to insert the elipsiss<br>
&lt;ydaniv> andreubotella: if you have a forced line break inside pre or nowrap then it forces to &lt;missed><br>
&lt;florian> andreubotella: and there is enough room at the end of the line to fit the ellipsis, that is allowed<br>
&lt;ydaniv> ... only when it doesn't fit and you try to find next oppertunity it tries to find it<br>
&lt;florian> andreubotella: it's only when the ellipsis doesn't fit and you're looking for a previous placement point that nowrap would require removing the whole content<br>
&lt;ydaniv> astearns: so editorially if not specified, could spec editor specify that?<br>
&lt;ydaniv> ... is there some reason why nowrap is specified that way?<br>
&lt;ydaniv> florian: my suspision is editorial accident<br>
&lt;ydaniv> astearns: proposed resolution is to clarify the interaction between nowrap and block elipssis<br>
&lt;astearns> ack fantasai<br>
&lt;ydaniv> fantasai: I would prefer to define this on the line clamp side<br>
&lt;ydaniv> ...  that opportunities don't exist unless we need to know where they are for other reason<br>
&lt;ydaniv> ... say it ignores them with in nowrap<br>
&lt;ydaniv> astearns: that's the safeset, wondering if it's enough<br>
&lt;ydaniv> fantasai: question whether the information is there and can be accessed<br>
&lt;ydaniv> florian: I think editors can take that, since me and fantasai are editors we could<br>
&lt;ydaniv> astearns: objections?<br>
&lt;ydaniv> ... none<br>
&lt;ydaniv> RESOLVED: clarify the interaction between nowrap and block elipssis<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12811#issuecomment-3303492945 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:17:50 UTC