Re: [csswg-drafts] [css-overflow] Line-clamp and approaches to ellipsis insertion (#10844)

What we're discussing is where the block overflow ellipsis text (which might not be an ellipsis) should show up visually in the line. The ellipsis is either a single character, or three characters whose visual order makes no difference, so unless I'm missing something, we can treat the ellipsis exactly the same as an arbitrary isolate, since what matters here isn't its inner directionality.

But in any case, here we might be cutting off text and adding the ellipsis in the middle of arbitrarily high levels of embedding. Is looking at the directionality (rather than the bidi embedding level) of the next character enough to predict the right behavior in such cases?

My insistence on framing this in terms of adding the ellipsis with some particular embedding level before UAX#9 step 3.4 is because that's the place in the bidi algorithm where implementations are going to place the ellipsis. There's no knowing where to elide text and place the ellipsis without line breaking, so if the ellipsis handling is treated as a transformation of the original source text, that could not be implemented straightforwardly. And given that at this point in the algorithm we know the bidi embedding level of the entire paragraph, it seems like that could be used as part of figuring out the ellipsis embedding level.

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


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

Received on Thursday, 5 December 2024 20:17:49 UTC