Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(55)

Side by Side Diff: third_party/WebKit/LayoutTests/imported/wpt/custom-elements/parser/parser-uses-registry-of-owner-document-expected.txt

Issue 2434563008: Import wpt@26c8d4e87448d1c4e5ebf2ddb4917c0633c201db (Closed)
Patch Set: Mark one more test as potentially timing out Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 This is a testharness.js-based test.
2 PASS HTML parser must not instantiate custom elements inside template elements
3 PASS HTML parser must not use the registry of the owner element's document insid e an iframe
4 PASS HTML parser must use the registry of the content document inside an iframe
5 PASS HTML parser must not instantiate a custom element defined inside an frame i n frame element's owner document
6 PASS HTML parser must use the registry of window.document in a document created by document.implementation.createHTMLDocument()
7 FAIL HTML parser must use the registry of window.document in a document created by document.implementation.createXHTMLDocument() assert_true: expected true got false
8 FAIL HTML parser must use the registry of window.document in a document created by new Document Illegal constructor
9 PASS HTML parser must use the registry of window.document in a document created by XMLHttpRequest
10 Harness: the test ran to completion.
11
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698