Skip to content

Commit 4001c55

Browse files
committed
Revert "Handle <string> values in keyframes-name rules. (#12985)"
This reverts commit 643d5f0.
1 parent 643d5f0 commit 4001c55

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

css-animations-1/Overview.bs

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -229,10 +229,6 @@ Declaring Keyframes</h2>
229229
the names are fully <a>case-sensitive</a>;
230230
two names are equal only if they are codepoint-by-codepoint equal.
231231
The <<custom-ident>> additionally excludes the ''animation-name/none'' keyword.
232-
The <<string>> should be treated as <<custom-ident>>, hence parsed as invalid if
233-
is one of the <a>CSS-wide keywords</a> or "default"; empty string is not allowed
234-
either. It's serialized as identifier when possible and as <<string>> otherwise.
235-
236232

237233
<div class=example>
238234
For example, the following two ''@keyframes'' rules have the same name,
@@ -258,8 +254,8 @@ Declaring Keyframes</h2>
258254
@keyframes None { /* ... */ }
259255
</pre>
260256

261-
They are also <em>invalid</em> if those names are specified with a <<string>>
262-
because they can not be serialized as valid <<custom-ident>>:
257+
However, those names <em>can</em> be specified with a <<string>>,
258+
so the following are both <em>valid</em>:
263259

264260
<pre class=lang-css>
265261
@keyframes "initial" { /* ... */ }

0 commit comments

Comments
 (0)