-- in a comment isn't an error

stevecheckoway · stevecheckoway · commit 2db78ecf5f76 · 2018-10-01T14:26:10.000-04:00
`&lt;!-- -- --&gt;` is not an error. The middle `--` cause the tokenizer to
enter the comment end state. The "anything else" clause appends two `-`
to the comment token's data and the current input character is
reconsumed in the comment state.
diff --git a/tree-construction/comments01.dat b/tree-construction/comments01.dat
@@ -29,7 +29,6 @@ FOO<!-- BAR --!>BAZ
 FOO<!-- BAR --   >BAZ
 #errors
 (1,3): expected-doctype-but-got-chars
-(1,15): unexpected-char-in-comment
 (1,21): eof-in-comment
 #new-errors
 (1:22) eof-in-comment
@@ -44,8 +43,6 @@ FOO<!-- BAR --   >BAZ
 FOO<!-- BAR -- <QUX> -- MUX -->BAZ
 #errors
 (1,3): expected-doctype-but-got-chars
-(1,15): unexpected-char-in-comment
-(1,24): unexpected-char-in-comment
 #document
 | <html>
 |   <head>
@@ -58,8 +55,6 @@ FOO<!-- BAR -- <QUX> -- MUX -->BAZ
 FOO<!-- BAR -- <QUX> -- MUX --!>BAZ
 #errors
 (1,3): expected-doctype-but-got-chars
-(1,15): unexpected-char-in-comment
-(1,24): unexpected-char-in-comment
 (1,31): unexpected-bang-after-double-dash-in-comment
 #new-errors
 (1:32) incorrectly-closed-comment
@@ -75,9 +70,6 @@ FOO<!-- BAR -- <QUX> -- MUX --!>BAZ
 FOO<!-- BAR -- <QUX> -- MUX -- >BAZ
 #errors
 (1,3): expected-doctype-but-got-chars
-(1,15): unexpected-char-in-comment
-(1,24): unexpected-char-in-comment
-(1,31): unexpected-char-in-comment
 (1,35): eof-in-comment
 #new-errors
 (1:36) eof-in-comment
