From 14d963127701f8d2c331aa00fef46eb9bc3c8c24 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javier=20Fern=C3=A1ndez=20Garc=C3=ADa-Boente?= Date: Mon, 20 Oct 2025 21:17:02 +0200 Subject: [PATCH] Handle values in keyframes-name rules. --- css-animations-1/Overview.bs | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/css-animations-1/Overview.bs b/css-animations-1/Overview.bs index 3b16f042f39..320e337e5a0 100644 --- a/css-animations-1/Overview.bs +++ b/css-animations-1/Overview.bs @@ -229,6 +229,10 @@ Declaring Keyframes the names are fully case-sensitive; two names are equal only if they are codepoint-by-codepoint equal. The <> additionally excludes the ''animation-name/none'' keyword. + The <> should be treated as <>, hence parsed as invalid if + is one of the CSS-wide keywords or "default"; empty string is not allowed + either. It's serialized as identifier when possible and as <> otherwise. +
For example, the following two ''@keyframes'' rules have the same name, @@ -254,8 +258,8 @@ Declaring Keyframes @keyframes None { /* ... */ } - However, those names can be specified with a <>, - so the following are both valid: + They are also invalid if those names are specified with a <> + because they can not be serialized as valid <>: 
 		@keyframes "initial" { /* ... */ }