Re: [csswg-drafts] [css-overflow-4] Should block-ellipsis clip ::before/::after text? (#11253)

The CSS Working Group just discussed `[css-overflow-4] Should block-ellipsis clip ::before/::after text?`, and agreed to the following:

* `RESOLVED: No special casing of ::before/::after, but keep open to investigate solutions for the use cases listed`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> andreubotella: Question is whether to clip ::before/::after content before the clip point<br>
&lt;fantasai> andreubotella: One use case was quotation marks. In this case, might want to put the ellipsis before the end quote<br>
&lt;florian> q+<br>
&lt;fantasai> andreubotella: But there are other use cases where it won't be as clear<br>
&lt;fantasai> andreubotella: There are some use cases for e.g. "click to see more", but you can't do that with pseudos anyway<br>
&lt;fantasai> andreubotella: I understand the use case for quotes, but it depends a lot, so I'm not sure<br>
&lt;fantasai> andreubotella: This would add some complications. For example, what if the pseudo has a forced line break<br>
&lt;astearns> ack florian<br>
&lt;emilio> q+<br>
&lt;fantasai> florian: I agree with close no change.<br>
&lt;fantasai> florian: If you really need for blockquotes, you can set the ellipsis string to ellipsis + endquote<br>
&lt;fantasai> florian: There's the case of nested quotations which is a bit complicated<br>
&lt;iank_> I agree - also don't want to change existing implementations.<br>
&lt;astearns> ack emilio<br>
&lt;fantasai> florian: but we can also consider expanding later, to add a keyword to append open quotations for example<br>
&lt;fantasai> emilio: Not objecting, but we should try to figure out a way to make some of these work.<br>
&lt;fantasai> emilio: Like the "Read more" button is not trivial to do together with ellipsis<br>
&lt;fantasai> emilio: So I agree with close no change with current behavior<br>
&lt;andreubotella> q+<br>
&lt;fantasai> emilio: but we should try to add something<br>
&lt;fantasai> florian: for the interactive reveal thing?<br>
&lt;fantasai> emilio: yeah<br>
&lt;fantasai> astearns: Maybe not close no change, but maybe close no special behavior for ::before/::after and keep open to solve some of the use cases<br>
&lt;astearns> s/close no special/resolve no special/<br>
&lt;astearns> ack andreubotella<br>
&lt;fantasai> andreubotella: [something about floats on last line]<br>
&lt;fantasai> emilio: I agree you want something *like* floats but .. don't have a great idea about how to do it right now<br>
&lt;fantasai> emilio: but in any case, we shouldn't special-case ::before and ::after<br>
&lt;emilio> astearns: elika, something to add?<br>
&lt;emilio> fantasai: the conclusion seems alright<br>
&lt;andreubotella> s/[something about floats on last line]/there's an issue to detect whether we're clamping, and maybe we could add a way to clamp on the last line?/<br>
&lt;fantasai> RESOLVED: No special casing of ::before/::after, but keep open to investigate solutions for the use cases listed<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
&lt;dbaron> (I wonder if there are any interesting cases with :beforre/:after and UI controls....<br>
</details>


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


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

Received on Tuesday, 27 January 2026 21:16:04 UTC