[css-overflow-4] Remove request to not expose line-clamp longhands #12400
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was only intended as a temporary "hold your horses" warning while we figured the syntax space, but the design has been stable for years at this point, and the notion of unexposed longhands brings its own set of complexity. See w3c#10439
emilio
approved these changes
Jun 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The request in the spec not to expose the longhands of line-clamp to authors was only intended as a temporary warning while we figured the syntax space, but the design has been stable for years at this point, and the notion of unexposed longhands brings its own set of complexity.
See #10439
@emilio, in #10439, we resolved on doing this, but you were not on the call, and we wanted to run this by you to make sure you had no objection, so I'm doing this as a PR rather than as a direct commit, so that you get a chance to pull the breaks if for some reason that's not something you're OK with.