- From: Javier Fernandez Garcia-Boente via GitHub <noreply@w3.org>
- Date: Wed, 04 Mar 2026 23:27:29 +0000
- To: public-css-archive@w3.org
> I'm not clear at this point what our resolution is, and what, if anything needs edits (specs and/or tests). My understanding is that the [resolution](https://github.com/w3c/csswg-drafts/issues/2435#issuecomment-428646888) means that the value of the 'animation-name' should be serialized as 'identifies' when possible, and as ```<string>``` otherwise. IMO, there is no need to touch the spec, which [states](https://drafts.csswg.org/css-animations/#at-ruledef-keyframes) as follows: > When serialized, the value is serialized as an [<ident>](https://drafts.csswg.org/css-values-4/#typedef-ident) unless it’s a disallowed keyword, in which case it’s serialized as a <string>. This is how Firefox and Safari interpreted the resolution mentioned before, so they adapted their implementation accordingly. I have recently implemented the same behavior in Chrome. However, the last comment mentions some lack of interop in other usages of the ```@keyframe``` value and some missing test cases. As far as I could understand, no spec change is needed. -- GitHub Notification of comment by javifernandez Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2435#issuecomment-4000946384 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 March 2026 23:27:30 UTC