-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
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
Make wpt own the HTML parser test data and remove dependency on html5lib-python, html5lib-tests #27868
Comments
this is effectively a dupe of html5lib/html5lib-tests#127 fwiw |
@gsnedders oh, right, I had forgotten about that! It seems like there isn't objection. Are you still planning to work on this? |
It is a long way down my list. |
A tweak we can make is to depend on |
One obvious (easy) tweak given it's using |
My main concern is that I want to preserve the file format for the preferred form form making modifications to the test, since there are non-WPT consumers of those formats. I'm not a fan of WPT having a build step that transforms the tree builder test format. FWIW, Gecko's mochitest harness stores the original .dat format in the repo and parses it when the tests are run. |
Having the sources files in the same format in wpt and parsing them with JS when running sounds ideal actually. Can that parser be migrated to wpt? |
Having worked on a parser bug in WebKit I now think this would be even more valuable than I previously thought. It looks like Chromium and WebKit both have two sets of parser tests in the tree:
And the former has tests the latter might not contain. I contributed further to this problem in WebKit/WebKit#12019, but am willing to be part of the cleanup crew if we make web-platform-tests the true home of HTML parser tests. I suspect @mfreed7 might be interested in this from the Chromium side. Copying here to gather interest. |
I'm definitely supportive of the effort to clean this up, and make WPT the source of truth for parser tests. |
Steps taken thus far:
I wonder if @zcorpan is still interested in taking this even further as I think it would definitely be preferable if we didn't have to go via html5lib-tests. https://github.com/html5lib/html5lib-tests does have a number of actionable issues and stale PRs worth triaging. Help appreciated. |
Yes. See html5lib/html5lib-tests#127 (comment) and later comments. |
@zcorpan any progress on this? |
Not yet but it's on my list. |
This week I've done the exercise of updating HTML parser tests again, though this time I was a bit more successful in figuring out how to get those changes through to wpt (see #2887). But boy is it painful and also mostly undocumented!
html5lib-tests
(in the custom test data format) Update existing tests and add new tests per spec change (<svg><p> in innerHTML) html5lib/html5lib-tests#133html5lib-python
's submodule ofhtml5lib-tests
AND update.pytest.expect
(manually?) so that html5lib itself doesn't fail the changed tests without having them marked as expected failures. Update tests/testdata (for <svg><p> in innerHTML) html5lib/html5lib-python#531html5lib-python
in wpt'shtml/tools/build.sh
and generate tests inwpt
by runninghtml/tools/build.sh
. HTML: Test <svg><p> in innerHTML: Sync with html5lib-tests#133 #27799Juggling 3 repos for one change like this doesn't seem ideal for contributors. From wpt's perspective, what I would like instead is:
wpt
and run a script to generate tests. No dependency on html5lib.Then
html5lib-python
can get the tree-builder test data fromwpt
instead of fromhtml5lib-tests
.Thoughts? @gsnedders @jgraham @annevk @stephenmcgruer
The text was updated successfully, but these errors were encountered: