Complete switch to upstream html5lib tests

Open fb55 opened this issue 3 years ago • 1 comments

With #447 and #449, we now run html5lib tests simultaneously with the forked tests. The remaining step is to drop the fork.

The remaining issue is a misalignment in error names between the upstream tests and the fork. We will have to figure out a way to map between the two.

Mar 12 '22 10:03 fb55

@fb55 it looks like the fork just introduces missing-doctype and non-conforming-doctype

are you suggesting we keep those errors but somehow patch the html5lib tests to include them?

should we just drop those errors? since the tests don't include them so i guess they're "non-standard"? 🤔 im a bit out of the loop on this

edit:

ah ok there's quite a few custom errors actually:

misplaced doctype
non-conforming doctype
end tag without matching open element
misplaced start tag for head element
open elements left after EOF
disallowed content in no script in head

etc

Jul 28 '25 21:07 43081j