-
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
HTML: Add tentative tests for speculative HTML parsing #24521
Conversation
ed26ec1
to
3849cc1
Compare
c500c87
to
92a9847
Compare
I'm done with adding new tests for now. If someone is interested in reviewing, I believe this is in a reviewable state (though there's no spec proposal yet). |
I forgot that the main meta charset scanner looks inside scripts per spec
…g the test markup
…r ignores encoding decl
04db284
to
b9339c8
Compare
Rebased again to resolve conflicts. The
I could reproduce this locally by reloading the test a couple of times in Firefox Nightly. @hsivonen is this a known issue? Or is 1500ms for the blocking script insufficient for stable test results? |
Increasing the time to 3000ms doesn't fix the flakiness when testing locally. I can submit a bug for Gecko. Edit: https://bugzilla.mozilla.org/show_bug.cgi?id=1729702 |
Not known. I'll try to catch this is rr. Thanks. |
Sorry for the delay re-reviewing the speculative parser stuff! These tests LGTM. So Chromium has about 15 tests that fail and would need attention. This one (meta-charset-script-src.tentative.html) passes for |
Thanks, @mfreed7 !
Good catch. So Firefox fails with this message:
Chrome and Safari:
See this comment for how So in Chrome and Safari, the URL character encoding for the I don't recall why the test expects windows-1252, right now. I'm not sure why Firefox doesn't fetch here. @hsivonen do you know? |
@mfreed7 can you approve this PR with GitHub's review feature (in the Files Changed tab), please? Then we can merge. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
On the document-write/meta-charset test: In https://github.com/whatwg/html/pull/5959/files#diff-41cf6794ba4200b839c53531555f0f3998df4cbb01a4d5cb0b94e3ca5e23947dR110885 it's specced that the speculative parser ignores the encoding declaration (because, changing the encoding can cause a re-navigation per spec). There was a bug in the test that I had fixed before but accidentally reverted, and now have fixed again (fc10383) -- the charset scanner shouldn't find the encoding declaration nested in a This fix doesn't change the test results, though. |
See whatwg/html#5624