Re: [csswg-drafts] [css-overflow-4] Syntax to opt into clamping at the earlier of a size and a number of line (#13670)

> Some possible suggestions for naming of 'block-ellipsis' to reduce my issue with redundancy.
> 
>     * `block-last-line: no-ellipsis | ellipsis | <string>`
> 
>     * `block-clamp: no-ellipsis | ellipsis | <string>`
> 
>     * `last-line: no-ellipsis | ellipsis | <string>`
> 
>     * `block-line: no-ellipsis | ellipsis | <string>`
> 
>     * `block-line-clamp: no-ellipsis | ellipsis | <string>`
> 
> 
> Of these I like `block-last-line` or `block-line-clamp` the best to get rid of the redundancy and it's in my opinion mirroring the spec text.

I don't really like any of these options, I don't think any of them make it clear what it is that they do. But `block-ellipsis` also might not make it too clear. I'd go for `line-clamp-ellipsis` if not for the redundancy. So maybe `line-clamp-marker`? Not sure.

-------

> Rather than doing `max-lines: none | [<integer> || auto]`, how about `max-lines: <integer> || auto`?

We never actually discussed this, and I think this is something the last resolution was ambiguous on.

In the last resolution, we decided to switch the keyword `auto` and the trigger for clamping by both lines and height to the `max-lines` property, instead of having it as part of `continue` as in Florian's original proposal. However, we didn't decide exactly how that would work.

A straightforward application of the decision we reached would be `none | [<integer> || auto]`, but `none` would only block clamping, which we can already do with `continue: none`. Instead, it makes a lot more sense to have the syntax space be `<integer> || auto`, with `auto` being the initial value. This would not change the `line-clamp` syntax.

@astearns Can we do an async resolution?

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


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

Received on Friday, 15 May 2026 15:42:04 UTC