Re: [csswg-drafts] [css-overflow] Bidi handling for text-overflow and line-clamp ellipses (#12617)

The CSS Working Group just discussed `[css-overflow] Bidi handling for text-overflow and line-clamp ellipses`, and agreed to the following:

* `RESOLVED: affirm the previous resolution is literally correct and we did indeed mean paragraph, not block`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> florian: previously, we resolved on bidi behavior of ellipsis<br>
&lt;TabAtkins> florian: we said both ellipses, talking about lbock-ellipsis and text-overflow<br>
&lt;TabAtkins> florian: [quote resolution]<br>
&lt;TabAtkins> florian: during that discussion we were ambiguously using the word "bidi paragraph" and "block"<br>
&lt;TabAtkins> florian: most of the time they're the same<br>
&lt;TabAtkins> florian: but if the value of unicode-bidi on the container is plaintext, then block and paragraph are not the same. so which do we want?<br>
&lt;TabAtkins> florian: this is really an edge case. only matter if you're using unicode-bidi, rare. and line-clamp on the plaintext element. and changed away from default ellipsis that contains a mix of neutrals and directional chars.<br>
&lt;TabAtkins> florian: if any of these fail it doesn't matter.<br>
&lt;TabAtkins> florian: here's an example<br>
&lt;TabAtkins> florian: most paragraphs are in English, so ellipsis is "...(continued)...", but one paragraph is in persian<br>
&lt;TabAtkins> florian: do you expect the ... to shift around the sides of the "(continued)"?<br>
&lt;TabAtkins> florian: I think we want first one, that means bidi paragraph, not blcok<br>
&lt;TabAtkins> astearns: hearing some yesses and nods<br>
&lt;kbabbitt> +1 to first one<br>
&lt;TabAtkins> florian: so we affirm the previous resolution is literally correct and we did indeed mean paragraph, not block<br>
&lt;TabAtkins> astearns: objections?<br>
&lt;TabAtkins> andreubotella: no objection. I think it's clearer to describe it as, rather than inheriting direction, we set it to match the paragraph direction.<br>
&lt;TabAtkins> florian: that was resolution language, not spec language<br>
&lt;TabAtkins> RESOLVED: affirm the previous resolution is literally correct and we did indeed mean paragraph, not block<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12617#issuecomment-4179739547 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 2 April 2026 18:39:01 UTC