[Feature Proposal] Track @keyframes support
#4
Closed
knowler
started this conversation in
Feature Proposal
Replies: 2 comments 1 reply
|
Thanks @knowler! This looks like a great addition. Feel free to open a PR if you have availability, otherwise we'll try to do it soon! Let me know your preference. Do you feel WPT adequately covers these issues? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Code of Conduct
Contributor License Agreement
Feature name
@keyframesWhy should we track this?
Animation is a common need and it’s not uncommon to want to style a shadow part or an element that’s slotted.
Shadow DOM behavior / expectation mismatches
Behaviour is inconsistent across browsers. Where you can use keyframes as an animation name depends on the context it’s defined in for some browsers. Here’s an example that enumerates a number of combinations of animations in the same context or between contexts: https://codepen.io/knowler/pen/qByVNOa
From my understanding of the spec
@keyframesshould now be tree-scoped names, so they should not leak out which means that Safari matches the expectation and Chrome Canary is getting closer. Firefox needs a little adjustments.animationcontext@keyframescontext::slotted())::slotted())::part())::part())Tested browsers:
Relevant links
All reactions