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

Btw, here's the text from the slides mentioned in the meeting notes:

<details>

> `line-clamp` syntax:
>
> ```text
> none | [<integer [1,∞]> || <'block-ellipsis'>] -webkit-legacy?
> ```
>
> ---
>
> - Left side (`none`)
>   - Disables clamping by setting all properties to their initial values
> - Right side (`[<integer [1,∞]> || <'block-ellipsis'>] -webkit-legacy?`)
>   - Sets `continue` to `auto` or `-webkit-legacy`, which enables clamping (maybe conditionally depending on legacy properties)
>   - `none` is a valid value of `block-ellipsis`, so **`none` is also a valid value for the right side**
>       - Meaning “clamp but don’t ellipsize”
>
> ---
> 
> **Proposal: drop `block-ellipsis: none`**
>
> - The allowed values would be `auto` (regular ellipsis) and `<string>`
> - If an author wants to have no ellipsis, they could achieve that with `block-ellipsis: ""`
>   - Currently `block-ellipsis: none` and `block-ellipsis: ""` behave differently if the line overflows, but that sounds like a spec bug
> 
> ---
> 
> **Implementation considerations**
> 
> - In Chromium, we were not planning on shipping `block-ellipsis: <string>` in the initial line-clamp rollout
> - With this change, `auto` would be the only possible value of `block-ellipsis` in the initial rollout
> - We might ship without `block-ellipsis` at first
> - That said, Samsung is working on implementing `text-overflow: <string>` in Chromium

</details>

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


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

Received on Friday, 22 August 2025 06:19:30 UTC