Re: [csswg-drafts] [css-animations] Serialize all keyframe names as strings (#2435)

The CSS Working Group just discussed `[css-animations] Serialize all keyframe names as strings`, and agreed to the following:

* `RESOLVED: No change to spec. Allowed keyframe names that can serialize as idents do so, and all others (requiring escapes or disallowed keywords like 'initial') serialize as strings.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> TabAtkins: Some discussions awhile back about exactly how keyframe names get serialized<br>
&lt;fantasai> TabAtkins: whether varies depends on keyframe name being an ident or some CSS-wide reserved keyword or something<br>
&lt;fantasai> TabAtkins: We had a resolution, and then backed that out<br>
&lt;fantasai> TabAtkins: I believe that browsers currently have interop on current spec<br>
&lt;fantasai> TabAtkins: which is that we serialize to a keyword if it doesn't require an escape and not a CSS-wide keyword<br>
&lt;fantasai> TabAtkins: If they need escapes or would match a disallowed keyword, we serialize as a string<br>
&lt;fantasai> TabAtkins: So I think we can close this issue as no change<br>
&lt;fantasai> RESOLVED: No change to spec. Allowed keyframe names that can serialize as idents do so, and all others (requiring escapes or disallowed keywords like 'initial') serialize as strings.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2435#issuecomment-4128067883 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 25 March 2026 16:37:49 UTC