Enable non-legacy line-clamp to work without special values
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: dshin, Assigned: salipov)
References
(Blocks 1 open bug)
Details
(Whiteboard: css-line-clamp, [wptsync upstream])
Attachments
(1 file)
... Unlike -webkit-line-clamp, this should not depend on display: -webkit-box | -webkit-inline-box and -webkit-box-orient.
For the purposes of incremental work, we're going to ignore custom/no ellipsis values here.
| Reporter | ||
Updated•1 month ago
|
| Assignee | ||
Updated•16 days ago
|
| Reporter | ||
Comment 1•10 days ago
|
||
Additional note, this part also needs to be rejiggered a bit here.
Namely, line-clamp container establishes an independent block formatting context. We need to make sure the above part of the code activates for non-legacy line-clamp, which likely involves avoiding this part if not legacy.
| Assignee | ||
Comment 2•9 days ago
|
||
Backed out for causing wr failures @ line-clamp-026.html
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/61384 for changes under testing/web-platform/tests
Upstream PR was closed without merging
| Assignee | ||
Comment 8•3 days ago
|
||
The test was failing on some platforms due to fuzz with text rendering. I have added a tolerance to this test.
Comment 10•2 days ago
|
||
| bugherder | ||
Upstream PR merged by moz-wptsync-bot
Upstream PR merged by moz-wptsync-bot
Description
•