Re: [csswg-drafts] [css-overflow-4] `line-clamp` shorthand syntax is ambiguous (#12416)

> 3. rename `none` from `max-lines` to something else. Downside: that's a pretty good name for what it does, not sure what else would work.

In isolation, I think a better keyword would be `auto` (since the value of `max-lines` is ignored if we're not clamping, and when it's set to `none` it clamps to however many lines will fit on the line-clamp container). But in the shorthand that would also be ambiguous with `block-ellipsis: auto`.

> 4. change the shorthand fro `none | [<integer [1,∞]> || <'block-ellipsis'>] -webkit-legacy?` to `none | [<integer [1,∞]> || <'block-ellipsis'> || <'continue'>] `, with `continue` being set to `collapse` when omitted, unless we're in the single `none` senario, in which case it is set to `auto`. Downside: now we have an ambiguity between `auto` in the shorthand meaning `continue: auto` or `block-ellipsis: auto` if the other is omitted.

I don't think this is a good idea, because if `continue` is set to `auto`, then there's no clamping, and the other two longhands are irrelevant. So you'd have `line-clamp: none` and `line-clamp: 3 auto` behaving the same.

---------

Looking at the options, I think (1) would probably be the best choice long-term. And since it doesn't seem like `block-ellipsis: none` would be used that much, it might be fine to not allow turning off the ellipsis at first.

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


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

Received on Wednesday, 16 July 2025 14:08:55 UTC