Skip to content

Commit 14d9631

Browse files
committed
Handle <string> values in keyframes-name rules.
1 parent a48d4f4 commit 14d9631

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

css-animations-1/Overview.bs

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -229,6 +229,10 @@ 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+
232236

233237
<div class=example>
234238
For example, the following two ''@keyframes'' rules have the same name,
@@ -254,8 +258,8 @@ Declaring Keyframes</h2>
254258
@keyframes None { /* ... */ }
255259
</pre>
256260

257-
However, those names <em>can</em> be specified with a <<string>>,
258-
so the following are both <em>valid</em>:
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>>:
259263

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

0 commit comments

Comments
 (0)