You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The line-clamp CSS property still needs a -webkit- prefix and some additional non-standard properties (display: -webkit-box and -webkit-box-orient: vertical) to be set in Chromium, WebKit and Firefox. Chromium is currently working on implementing the unprefixed property. Implementing this new standardized property, which differs significantly from the old non-standard -webkit-line-clamp property, likely needs a lot of work from an implementation standpoint.
This issue is one of seven issues regarding unprefixing CSS properties/values, originally all in #702 (as per #702 (comment)). The aim is to group the properties together into multiple (but not seven) focus areas.
Reacted by Gary Gozlan, John P. Green, Christopher Kirk-Nielsen, Shalanah Dawson, Ana Tudor, Oliver Williams, Nilesh Prajapati, Jun Shindo, Oyama Michinoku, Jon Rimmer and 37 more
The line-clamp property (sans prefixes) should not be supported unless anything it relies on also is cleaned up and does not require prefixes. Anyone using CSS.supports() would end up getting confused. I clarified the details when I posted my thread.
It's called Blink, not Chromium; Chromium is a browser, not a rendering engine.
I am very well aware of the difference between Chromium and Blink. Blink is a part of the Chromium project and inseparably tied to it. If you want to look at Blink's source code, you'll land in the Chromium repository. When creating Interop issues, it is important that people who are not deeply familiar with Chromium's internal structure also understand what I'm talking about. Chromium is the de facto umbrella term that also includes Blink and that—contrary to "Blink"—is very well known.
The line-clamp property (sans prefixes) should not be supported unless anything it relies on also is cleaned up and does not require prefixes.
Yes, this is what this issue is about. "Unprefixing line-clamp" refers to much more than just to change the property name in Blink's source code from -webkit-line-clamp to line-clamp. It means to implement an entirely new thing that doesn't depend on any other -webkit- stuff (see the linked specification).
@ccpandhare
Thank you! I added these to the original comment.
There are also some tests in other parts of css/ that test the interaction of (-webkit-)line-clamp with other properties. We don't need to include all of them, but I list them here for completeness:
Thank you for proposing Unprefixed line-clamp for inclusion in Interop 2025.
We wanted to let you know that this proposal was not selected to be part of Interop this year.
On behalf of the entire Interop team, thank you for submitting this proposal for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2025.
@jabcreations I've been closing issues using the default action, but certainly line-clamp isn't "completed" on the web platform. As one of the last remaining CSS properties that requires a prefix, it keeps popping up on my radar, going back to at least #16. I think it will stay on the radar of the Interop team, but it does help to see that there's a lot of demand for it.
One thing that came up in the planning process was w3c/csswg-drafts#10816, which is still in review. I will ask if there are other spec or test issues that relate to this proposal.
Another thing that happened not long ago is that Safari 18.2 shipped support for unprefixed line-clamp, which I found by following clues from https://webstatus.dev/features/line-clamp and testing to confirm. Surprisingly it isn't mentioned in the release notes. Testing this implementation and filing bugs would also be useful, I think.
There is also a WIP implementation in Chrome. It's not under the experimental web platform features flag yet, but you can test it with the --enable-blink-features=CSSLineClamp command-line flag.
Edit: My bad, it is enabled with experimental web platform features, and has been for months!
Activity
gsnedders commentedon Sep 18, 2024
See also #16 and discussion there from prior years.
bfgeek commentedon Sep 18, 2024
Note the new collapse variant specification is here:
w3c/csswg-drafts#10816
bfgeek commentedon Sep 18, 2024
If this goes through it should only be for
line-clampand not the individual sub-properties yet (max-lines,continue, etc).jabcreations commentedon Oct 4, 2024
It's called Blink, not Chromium; Chromium is a browser, not a rendering engine.
#775
The line-clamp property (sans prefixes) should not be supported unless anything it relies on also is cleaned up and does not require prefixes. Anyone using CSS.supports() would end up getting confused. I clarified the details when I posted my thread.
ccpandhare commentedon Oct 8, 2024
We (@rich-hansen, @ccpandhare) were planning to submit this exact proposal but found yours. Adding our "Additional Signals" section below:
BenjaminAster commentedon Oct 8, 2024
@jabcreations
I am very well aware of the difference between Chromium and Blink. Blink is a part of the Chromium project and inseparably tied to it. If you want to look at Blink's source code, you'll land in the Chromium repository. When creating Interop issues, it is important that people who are not deeply familiar with Chromium's internal structure also understand what I'm talking about. Chromium is the de facto umbrella term that also includes Blink and that—contrary to "Blink"—is very well known.
Yes, this is what this issue is about. "Unprefixing line-clamp" refers to much more than just to change the property name in Blink's source code from
-webkit-line-clamptoline-clamp. It means to implement an entirely new thing that doesn't depend on any other-webkit-stuff (see the linked specification).@ccpandhare
Thank you! I added these to the original comment.
andreubotella commentedon Oct 8, 2024
There are some additional tests for the parsing of
line-clamp-related properties in https://github.com/web-platform-tests/wpt/tree/ec979384f0340b8d18c3512f02f42b65bd5f456c/css/css-overflow/parsing.There are also some tests in other parts of
css/that test the interaction of(-webkit-)line-clampwith other properties. We don't need to include all of them, but I list them here for completeness:css/css-flexbox/alignment/flex-align-baseline-line-clamp-{001,002,003}.tentative.htmlcss/css-grid/alignment/grid-align-baseline-line-clamp-{001,002,003}.tentative.htmlcss/css-inline/baseline-source/baseline-source-{first,last}-{001,002,003}.html(includes-webkit-line-clampas one of the multiple tests)css/css-inline/text-box-trim:css/css-inline/text-box-trim/text-box-trim-line-clamp-001.htmlcss/css-inline/text-box-trim/text-box-trim-line-clamp-auto-{001,002}.html.autotests check for a non-trivial interaction that's not necessarily clear from the specs.css-text/white-space:css-text/white-space/text-wrap-balance-005.htmlcss-text/white-space/text-wrap-balance-line-clamp-001.htmlstubbornella commentedon Nov 21, 2024
Why? Do they need standards work?
wpt-interop commentedon Feb 13, 2025
Thank you for proposing Unprefixed
line-clampfor inclusion in Interop 2025.We wanted to let you know that this proposal was not selected to be part of Interop this year.
On behalf of the entire Interop team, thank you for submitting this proposal for consideration. We got many more proposals than we could include in this year's project, necessitating some difficult choices. Please note this should not be taken as a comment on the technology as a whole, or our willingness to consider it for Interop in the future. We appreciate the work you put into your proposal, and would welcome your participation in future rounds of Interop.
For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2025.
Posted on behalf of the Interop team.
jabcreations commentedon Feb 17, 2025
Closed as completed when it clearly wasn't? So everyone here will have to double their time spent to advocate for this again in ~10 months time?
foolip commentedon Feb 17, 2025
@jabcreations I've been closing issues using the default action, but certainly
line-clampisn't "completed" on the web platform. As one of the last remaining CSS properties that requires a prefix, it keeps popping up on my radar, going back to at least #16. I think it will stay on the radar of the Interop team, but it does help to see that there's a lot of demand for it.One thing that came up in the planning process was w3c/csswg-drafts#10816, which is still in review. I will ask if there are other spec or test issues that relate to this proposal.
Another thing that happened not long ago is that Safari 18.2 shipped support for unprefixed
line-clamp, which I found by following clues from https://webstatus.dev/features/line-clamp and testing to confirm. Surprisingly it isn't mentioned in the release notes. Testing this implementation and filing bugs would also be useful, I think.andreubotella commentedon Feb 17, 2025
There is also a WIP implementation in Chrome.
It's not under the experimental web platform features flag yet, but you can test it with the--enable-blink-features=CSSLineClampcommand-line flag.Edit: My bad, it is enabled with experimental web platform features, and has been for months!