feat: add @keyframes name parsing
#35903
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
requested review from
birtles,
dbaron,
grorg,
plinss and
tabatkins
yisibl
force-pushed
the
add-keyframes-name-parsing
branch
from
a4b8a9d to
ce1a1d1
Compare
I and @CGQAQ are working on implementing interoperability of `<keyframes-name>` across browsers The Chromium patch[1] requires this test [1]: https://chromium-review.googlesource.com/c/chromium/src/+/3865188
yisibl
force-pushed
the
add-keyframes-name-parsing
branch
from
ce1a1d1 to
9dfc9ca
Compare
dbaron
reviewed
Sep 15, 2022
dbaron
approved these changes
Sep 16, 2022
|
Thanks @dbaron |
This was referenced Sep 17, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I and @CGQAQ are working on implementing interoperability of
<keyframes-name>across browsersThe Chromium patch requires this test