We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I think abrupt-closing-of-empty-comment ('<!-->' and '<!--->') should be treated as normal comments in prescan as well.
abrupt-closing-of-empty-comment
'<!-->'
'<!--->'
for '<!-->', the spec states rather explicitly.
The two 0x2D bytes can be the same as those in the '<!--' sequence.'
prescan: https://html.spec.whatwg.org/multipage/parsing.html#prescan-a-byte-stream-to-determine-its-encoding abrupt-closing-of-empty-comment: https://html.spec.whatwg.org/multipage/parsing.html#parse-error-abrupt-closing-of-empty-comment
C.f. jsdom/html-encoding-sniffer has the same bug. jsdom/html-encoding-sniffer#4 Validator treats them as comments.
jsdom/html-encoding-sniffer
Validator
The text was updated successfully, but these errors were encountered:
Confirmed the spec says to treat them as comments.
Sorry, something went wrong.
No branches or pull requests
I think
abrupt-closing-of-empty-comment
('<!-->'
and'<!--->'
)should be treated as normal comments in prescan as well.
for
'<!-->'
, the spec states rather explicitly.prescan:
https://html.spec.whatwg.org/multipage/parsing.html#prescan-a-byte-stream-to-determine-its-encoding
abrupt-closing-of-empty-comment:
https://html.spec.whatwg.org/multipage/parsing.html#parse-error-abrupt-closing-of-empty-comment
C.f.
jsdom/html-encoding-sniffer
has the same bug.jsdom/html-encoding-sniffer#4
Validator
treats them as comments.The text was updated successfully, but these errors were encountered: