Skip to content

Commit 08ea4a7

Browse files
squeek502domenic
authored andcommitted
Fix description of missing-semicolon-after-character-reference error
The previous description was incorrect: `&notin` without a semicolon will not be parsed as "∉" because `&notin` without a semicolon is not included in the first column of the named character references table.
1 parent 672db03 commit 08ea4a7

File tree

1 file changed

+12
-8
lines changed

1 file changed

+12
-8
lines changed

source

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -126702,14 +126702,18 @@ dictionary <dfn dictionary>StorageEventInit</dfn> : <span>EventInit</span> {
126702126702
<td><dfn data-x="parse-error-missing-semicolon-after-character-reference">missing-semicolon-after-character-reference</dfn>
126703126703
<td>
126704126704
<p>This error occurs if the parser encounters a <span data-x="syntax-charref">character
126705-
reference</span> that is not terminated by a U+003B (;) <span>code point</span>. Usually the
126706-
parser behaves as if character reference is terminated by the U+003B (;) code point; however,
126707-
there are some ambiguous cases in which the parser includes subsequent code points in the
126708-
character reference.</p>
126709-
126710-
<p class="example">For example, <code data-x="">&amp;not;in</code> will be parsed as "<code
126711-
data-x="">&not;in</code>" whereas <code data-x="">&amp;notin</code> will be parsed as "<code
126712-
data-x="">&notin;</code>".</p>
126705+
reference</span> that is not terminated by a U+003B (;) <span>code point</span>.
126706+
The parser behaves the same as if the character reference is terminated by the U+003B
126707+
(;) code point.</p>
126708+
126709+
<p class="note">Most <span>named character references</span> require a terminating U+003B
126710+
(;) <span>code point</span>. Those that don't might get resolved as a longer named <span
126711+
data-x="syntax-charref">character reference</span> in certain ambiguous scenarios.</p>
126712+
126713+
<p class="example">For example, <code data-x="">&amp;notin</code> will be parsed as "<code
126714+
data-x="">&not;in</code>", i.e., the same as if the input were <code
126715+
data-x="">&amp;not;in</code>, whereas <code data-x="">&amp;notin;</code> will be parsed as
126716+
"<code data-x="">&notin;</code>".</p>
126713126717

126714126718
<tr>
126715126719
<td><dfn data-x="parse-error-missing-whitespace-after-doctype-public-keyword">missing-whitespace-after-doctype-public-keyword</dfn>

0 commit comments

Comments
 (0)