Re: [csswg-drafts] [css-overflow] Is continue: discard working in the fragment tree useful? (#7708)

>> 20. How do you insert the ellipsis text on the last line that remains:
>>     1. Does it remove text in logical or visual order (before/after bidi reordering)?
>>     2. Where does the ellipsis get placed, if inserted in a complicated bidi phrase?
>>     3. To make room for the ellipsis text, do we remove any number of individual grapheme cluster or do we respect the various css-text properties governing what are acceptable line-breaking opportunities?
>>     4. Is the content removed from the last line to make room for the ellipsis pushed to the discarded lines? That could for example be observed through the static position of abspos elements anchored in the discarded/collapsed content.
>>     5. Is the ellipsis text drawn in the block's font/font-size, the removed text's font/font-size, or something else?
>>     6. Does  ellipsis text affect the height of the line it's injected in if it happens to be the tallest (or only thing) on that line?
>>     7. What happens if ellipsis text is too long to fit the line?
> 

> 
> These questions don't seem specific to the "collapse" behaviour.

They are. The spec currently [answers this questions](https://drafts.csswg.org/css-overflow-4/#block-ellipsis) by assuming `continue: discard`, and in particular the insertion of the ellipsis is a layout affecting operation, in order to properly deal with bidi. It also gives some control over how the insertion works through the various properties that control text wrapping. As `continue: collapse` as described so far is primarily a paint-time effect (except for sizing the container), I don't see an obvious way to make the spec's provisions apply, so specific answers are needed.

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


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

Received on Wednesday, 11 October 2023 09:30:21 UTC