Re: [csswg-drafts] [css-overflow-4] Unexpected behavior of `continue: discard` on multicolumn containers with spanners (#8721)

@mstensho it's a bit of a long story. The short version of it is that both `continue: collapse` and `continue: discard` could be used as a foundation for building `line-clamp`. `continue: collapse` is simpler to implement, and in simple cases (flow content, not in a multi-col, without floats, without box decorations…), the result is effectively the same, so we're building the line-clamp on top of `continue-collapse` by default. Often enough the observable differences between the two don't matter, however, in more complicated cases, `continue: collapse` and `continue: discard` do result in different results, and `continue: discard`, being build on top of fragmentation, is more versatile. So the plan is to build and ship `line-clamp` using `continue: collapse`, but to continue exploring, at a lower priority, the avenues opened up by `continue: discard`. @andreubotella has built prototypes of both approaches, though his implementation of `continue: collapse` is a lot more complete.

(In a yet further future, `continue: discard` might also be a stepping stone towards the sort of things sketched out in [`continue: fragments`](https://drafts.csswg.org/css-overflow-5/#fragmentation))

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


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

Received on Monday, 15 September 2025 07:44:28 UTC