From 0f1fe17bb259a9d4cb9fa04e93ad5f23d6c6250c Mon Sep 17 00:00:00 2001
From: Javier Fernandez Garcia-Boente <jfernandez@igalia.com>
Date: Tue, 21 Oct 2025 16:48:18 +0200
Subject: [PATCH] Revert "Handle <string> values in keyframes-name rules.
 (#12985)"

This reverts commit 643d5f0111d212dc74d581aa68ba53e7b177a96f.
---
 css-animations-1/Overview.bs | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/css-animations-1/Overview.bs b/css-animations-1/Overview.bs
index 320e337e5a0..3b16f042f39 100644
--- a/css-animations-1/Overview.bs
+++ b/css-animations-1/Overview.bs
@@ -229,10 +229,6 @@ Declaring Keyframes</h2>
 	the names are fully <a>case-sensitive</a>;
 	two names are equal only if they are codepoint-by-codepoint equal.
 	The <<custom-ident>> additionally excludes the ''animation-name/none'' keyword.
-	The <<string>> should be treated as <<custom-ident>>, hence parsed as invalid if
-	is one of the <a>CSS-wide keywords</a> or "default"; empty string is not allowed
-	either. It's serialized as identifier when possible and as <<string>> otherwise.
-
 
 	<div class=example>
 		For example, the following two ''@keyframes'' rules have the same name,
@@ -258,8 +254,8 @@ Declaring Keyframes</h2>
 		@keyframes None { /* ... */ }
 		</pre>
 
-		They are also <em>invalid</em> if those names are specified with a <<string>>
-		because they can not be serialized as valid <<custom-ident>>:
+		However, those names <em>can</em> be specified with a <<string>>,
+		so the following are both <em>valid</em>:
 
 		<pre class=lang-css>
 		@keyframes "initial" { /* ... */ }