Re: [csswg-drafts] [css-overflow] Questions regarding breaks in ellipsis strings (#11660)

> However, I suspect the ellipsis should be treated as bidi isolated, so it doesn't reorder with the preceding inline content

The spec says:
> This inline is assigned [unicode-bidi: plaintext](https://drafts.csswg.org/css-writing-modes-3/#propdef-unicode-bidi)

`unicode-bidi: plaintext` does cause bidi isolation, so that's covered already.

> Yeah, unless there's some compat requirement, I expect the two ellipsises should work the same.

I am not sure this is a good assumption to make, in general. `text-overflow` is meant to be a paining effect, which can handled the overflowing content being scrolled in and out of view. `block ellipsis` is meant to integrate with line breaks. There may be some overlap in some behavior, and gratuitous divergence is not desirable, but the constraints are different.

That said, the definition of `test-overflow: ellipsis` does say:
> Ellipsing only affects rendering and must not affect layout 

There are various other aspects of the spec which hint that `test-overflow: ellipsis` is intended as a paint-time effect, and so there cannot possibly be any interaction with layout, bidi, fragmentation…

The Chrome implementation is known to diverge from that spec somewhat, and I think it is done with some degree of integration into layout. That has yet to be raised against the spec or resolved, but I don't expect it would (deliberately) be different about isolating bidi reordering in the string from bidi-reordering on the rest of the line.

@xiaochengh, does that answer your question?

We might want to add a small clarification in the spec(s) that bidi-reordering *within* the ellipsis is allowed.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11660#issuecomment-3336993160 using your GitHub account


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

Received on Friday, 26 September 2025 06:35:19 UTC