Skip to content
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

custom-elements: HTML parser should support customized <html>. #9406

Merged
merged 1 commit into from Feb 6, 2018

Conversation

Projects
None yet
4 participants
@chromium-wpt-export-bot
Copy link
Collaborator

chromium-wpt-export-bot commented Feb 6, 2018

HTMLConstructionSite::InsertHTMLHtmlStartTagBeforeHTML() should use
"create an element" algorithm.

Test: Update builtin-coverage.html so that it tests elements parsed by
the document parser if they are unable to be tested with innerHTML
setter. Now it can test <html is=> and <body is=>.

Bug: 808311
Change-Id: I511edfa28750210d39b9e9a0fb711e245dc5737d
Reviewed-on: https://chromium-review.googlesource.com/903345
Reviewed-by: Yoshifumi Inoue yosin@chromium.org
Commit-Queue: Kent Tamura tkent@chromium.org
Cr-Commit-Position: refs/heads/master@{#534655}

@wpt-pr-bot
Copy link
Collaborator

wpt-pr-bot left a comment

Already reviewed downstream.

@w3c-bots

This comment has been minimized.

Copy link

w3c-bots commented Feb 6, 2018

Build PASSED

Started: 2018-02-06 08:00:05
Finished: 2018-02-06 08:05:41

This report has been truncated because the number of unstable tests exceeds GitHub.com's character limit for comments (65536 characters).

Failing Jobs

  • safari:11.0

Unstable Browsers

Browser: "Safari 11.0" (failures allowed)

View in: WPT PR Status | TravisCI

custom-elements: HTML parser should support customized <html>.
HTMLConstructionSite::InsertHTMLHtmlStartTagBeforeHTML() should use
"create an element" algorithm.

Test: Update builtin-coverage.html so that it tests elements parsed by
the document parser if they are unable to be tested with innerHTML
setter. Now it can test <html is=> and <body is=>.

Bug: 808311
Change-Id: I511edfa28750210d39b9e9a0fb711e245dc5737d
Reviewed-on: https://chromium-review.googlesource.com/903345
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534655}

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-903345 branch from 1890454 to 7c28143 Feb 6, 2018

@chromium-wpt-export-bot chromium-wpt-export-bot merged commit f36a063 into master Feb 6, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-903345 branch Feb 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.