- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 14:00:31 +0000
- To: public-css-archive@w3.org
> [@frivoal](https://github.com/frivoal) how would you envision this to work if `line-clamp` _and_ `-webkit-line-clamp` are expected both to be shorthands, but none of its longhands are exposed? As I was saying, the spec's note about not exposing the long hands was meant as a precaution early in the design, to avoid locking ourselves into something we might want to change. It was not meant as a permanent ban. Given that we have done a quite significant revision to the design, and that the syntax space is barely affected, I'm thinking we might want to lift the restriction on the long hands, and just allow them to be exposed normally. > The right interim situation, IMO, is making `line-clamp` a longhand. `-webkit-line-clamp` will be a shorthand for `line-clamp`. When we're ready to expose the different shorthands, we can turn `line-clamp` into a shorthand of those properties. Otherwise the OM is inconsistent, I don't think there's a concept for "shorthand of unspecified longhands", and I'd rather not invent that, since it would effectively be just a longhand. Agreed. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10439#issuecomment-3004892470 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 June 2025 14:00:32 UTC