Re: [csswg-drafts] [css-overflow-4] How do `-webkit-line-clamp` and `line-clamp` interact when both are specified? (#10439)

> Should -webkit-line-clamp, which was previously behaving like a longhand in getComputedStyle(), switch to behaving like a shorthand?

I'd say yes

> Should line-clamp behave like a shorthand, given that it's currently specified as a shorthand even though its longhands shouldn't be exposed, since the plan is to expose them in the future.

I'd say yes. On top of that, we had said several years ago that we were choosing not to expose the longhangs to keep ourselves some flexibility in case we wanted to change their name or syntax. In the meanwhile, there's been significant rework of the proposal (with the introduction of `collapse` and all), but the syntax has staid stable the whole time, with no counter-proposal. I think we might want to lift that restriction on the longhands, and just have them be regular longhands.

Also, one more question:
Since `line-clamp` now also has a value of `-webkit-legacy`, we have a choice: `-webkit-line-clamp` can be a shorthand of the same longhands as line-clamp (what we've said so far), or it could be a shorthand of `line-clamp` itself. Initially, it had to be a shorthand of the longhands, since there was not `-webkit-legacy` keyword on `line-clamp`, but now there is. Which one do we want to go with?

I don't care strongly either way, but it's a choice we now have, so I thought I'd ask.


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


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

Received on Friday, 6 June 2025 03:47:18 UTC