- From: Andreu Botella via GitHub <noreply@w3.org>
- Date: Wed, 13 Aug 2025 15:54:29 +0000
- To: public-css-archive@w3.org
> That note is about `block-ellipsis`. `text-overflow` has different mechanics. I don't think they're different enough. There's a lot of common behavior that's expressed in different words – for example, I think this `line-height: 0` behavior for `block-ellipsis` is included in the "Ellipsing only affects rendering and must not affect layout" spec text for `text-overflow`. I think whatever solution we end up choosing for `text-overflow` should also apply to `block-ellipsis`; but I'm not sure that clamping the ellipsis text itself is a good idea. I'd say that if the string text has a forced line break, this is almost certainly a bug by the web developer; but since the presence of a forced line break depends on `white-space-collapse`, this isn't something that can be detected at parse time. Given that, an option could be to fall back into behaving like `text-overflow: clip` in that case. But another option would be to treat the string as ending at the first forced break – essentially @SebastianZ's proposal of clipping it to be one line high, but without (re?)ellipsizing it. -- GitHub Notification of comment by andreubotella Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12557#issuecomment-3184486584 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 August 2025 15:54:29 UTC