[css-overflow-3] should -webkit-discard be a valid value for continue? #6842
Assignees
Labels
Closed Accepted as Editorial
Commenter Satisfied
Commenter has indicated satisfaction with the resolution / edits.
css-overflow-3
Current Work
Comments
|
The spec's intent is that it is a valid value of the continue property, but since it's only there for legacy compat, it's described in a compatibility subsection rather than in the main body of text. The current write up means it as an editorial tweak to deemphasize that value, but it is still mean to behave perfectly normally, excatly as if it had. But I can see how that's not obvious. I've just pushed an editorial update to that section that hopefully should avoid this confusion. Let me know if that works for you. |
frivoal
added a commit
that referenced
this issue
Dec 22, 2021
The -webkit- prefixed compat part of line-clamp and related properties aren't meant to be anything out of ordinary in terms of property mechanics, cascading, OM, etc. They're defined in a separate section do deemphasize them, but otherwise behave normally. The previous description was confusing about that, so this clarifies that. See #6842
|
Yeah, I think this works for me. |
frivoal
added
Commenter Satisfied
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://drafts.csswg.org/css-overflow-3/#propdef-continue / https://drafts.csswg.org/css-overflow-3/#valdef-continue--webkit-discard
Per the value grammar for
continue,-webkit-discardis not a valid value, despite it being set as the value ofcontinueby the-webkit-line-clampshorthand.I'm unaware of any other case where a property has a value that can only be set via a shorthand, hence this feels like it's adding an oddity (and quite probably causing extra implementation complexity as a result, for unclear benefit to anyone).
It's also somewhat surprising that a value for
continueis defined within the "Limiting Visible Lines: the line-clamp shorthand property" section, without "Fragmentation of Overflow: the continue property" even mentioning that value.Also, if the computed value of
continueis-webkit-discard(via the shorthand), how do we expectcontinueto serialise? Do we expect it to serialise to an invalid value, or to what?The text was updated successfully, but these errors were encountered: