Open
Bug 1533327
Opened 5 years ago
Updated 1 month ago
revert/revert-layer behaves as unset in @keyframes rules
Categories
(Core :: CSS Parsing and Computation, enhancement, P3)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: emilio, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
|
842 bytes,
text/plain
|
Details |
This doesn't work in WebKit either, and per the commit message in bug 1215878, I don't think it's worth it, honestly, since it requires us to hackily re-implement revert in another codepath, and WebKit and Blink cannot even fix it. Happy to change my mind about this though.
Here's a WPT test that tests this.
|
Reporter | |
Updated•5 years ago
|
Summary: revert doesn't work in @keyframes rules → revert behaves as unset in @keyframes rules
|
||
Updated•5 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
|
|
Reporter | |
Updated•10 months ago
|
Summary: revert behaves as unset in @keyframes rules → revert/revert-layer behaves as unset in @keyframes rules
|
||
Comment 3•7 months ago
•
|
||
I think this is the reason we're failing https://wpt.fyi/results/css/css-cascade/revert-layer-010.html and https://wpt.fyi/results/css/css-cascade/presentational-hints-rollback.html (which appear on the interop2023 dashboard's previous focus areas).
You need to log in
before you can comment on or make changes to this bug.
Description
•