third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt - Issue 2881323002: Support Document constructor.

Unified Diff: third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt

Issue 2881323002: Support Document constructor. (Closed)

Patch Set: add svg/xml tests Created 3 years, 7 months 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 side-by-side diff with in-line comments

« no previous file with comments | « third_party/WebKit/LayoutTests/external/wpt/custom-elements/parser/parser-uses-registry-of-owner-document-expected.txt ('k') | third_party/WebKit/LayoutTests/external/wpt/dom/events/Event-dispatch-bubbles-false-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt

diff --git a/third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt b/third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt

deleted file mode 100644

index 4fedcfe6823462ff0b672a27c4c909271f050fa3..0000000000000000000000000000000000000000

--- a/third_party/WebKit/LayoutTests/external/wpt/custom-elements/upgrading-expected.txt

+++ /dev/null

@@ -1,28 +0,0 @@

-This is a testharness.js-based test.

-PASS Creating an element in the document of the template elements must not enqueue a custom element upgrade reaction because the document does not have a browsing context

-PASS Creating an element in the document of the template elements and inserting into the document must not enqueue a custom element upgrade reaction

-PASS Creating an element in the document of the template elements and adopting back to a document with browsing context must enqueue a custom element upgrade reaction

-FAIL Creating an element in a new document must not enqueue a custom element upgrade reaction because the document does not have a browsing context promise_test: Unhandled rejection with value: object "TypeError: Illegal constructor"

-FAIL Creating an element in a new document and inserting into the document must not enqueue a custom element upgrade reaction promise_test: Unhandled rejection with value: object "TypeError: Illegal constructor"

-FAIL Creating an element in a new document and adopting back to a document with browsing context must enqueue a custom element upgrade reaction promise_test: Unhandled rejection with value: object "TypeError: Illegal constructor"

-PASS Creating an element in a cloned document must not enqueue a custom element upgrade reaction because the document does not have a browsing context

-PASS Creating an element in a cloned document and inserting into the document must not enqueue a custom element upgrade reaction

-PASS Creating an element in a cloned document and adopting back to a document with browsing context must enqueue a custom element upgrade reaction

-PASS Creating an element in a document created by createHTMLDocument must not enqueue a custom element upgrade reaction because the document does not have a browsing context

-PASS Creating an element in a document created by createHTMLDocument and inserting into the document must not enqueue a custom element upgrade reaction

-PASS Creating an element in a document created by createHTMLDocument and adopting back to a document with browsing context must enqueue a custom element upgrade reaction

-PASS Creating an element in an HTML document created by createDocument must not enqueue a custom element upgrade reaction because the document does not have a browsing context

-PASS Creating an element in an HTML document created by createDocument and inserting into the document must not enqueue a custom element upgrade reaction

-PASS Creating an element in an HTML document created by createDocument and adopting back to a document with browsing context must enqueue a custom element upgrade reaction

-PASS Creating an element in an HTML document fetched by XHR must not enqueue a custom element upgrade reaction because the document does not have a browsing context

-PASS Creating an element in an HTML document fetched by XHR and inserting into the document must not enqueue a custom element upgrade reaction

-PASS Creating an element in an HTML document fetched by XHR and adopting back to a document with browsing context must enqueue a custom element upgrade reaction

-PASS Creating an element in the document of an iframe must not enqueue a custom element upgrade reaction if there is no matching definition

-PASS Creating an element in the document of an iframe must enqueue a custom element upgrade reaction if there is a matching definition

-PASS "define" in the document of an iframe must not enqueue a custom element upgrade reaction on a disconnected unresolved custom element

-PASS Inserting an unresolved custom element into the document of an iframe must enqueue a custom element upgrade reaction

-PASS "define" in the document of an iframe must enqueue a custom element upgrade reaction on a connected unresolved custom element

-PASS Adopting (and leaving disconnceted) an unresolved custom element into the document of an iframe must not enqueue a custom element upgrade reaction

-PASS Adopting and inserting an unresolved custom element into the document of an iframe must enqueue a custom element upgrade reaction

-Harness: the test ran to completion.