Closed fb55 closed 2 years ago
In fact if you check the spec, ¬i..
is the exact example they use to describe that edgecase: https://html.spec.whatwg.org/multipage/parsing.html#named-character-reference-state:
if the markup contains the string I'm ¬it; I tell you in an attribute, no character reference is parsed and string remains intact (and there is no parse error).
Thanks a lot for flagging @untitaker. I've reverted the additions.
error locations are not actually standardized, right? this is just to make the testsuite internally consistent?
error locations are not actually standardized, right? this is just to make the testsuite internally consistent?
That is correct.
@Ms2ger It would be great if you could have another look at this (as well as #145 if possible)!
I am trying to move parse5 to the upstream html5lib-tests repo (away from this fork). As a first PR to come from this effort, this PR corrects some tokenizer errors. The changes are in three categories:
Reverted.unknown-named-character-reference
errors were missing entirely and have been added.