Closed Bug 1602198 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 16348 - Adoption and DocumentFragment

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla73
Tracking Status
firefox73 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 16348 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/16348
Details from upstream follow.

Anne van Kesteren <annevk@annevk.nl> wrote:

Adoption and DocumentFragment

Tests for https://github.com/whatwg/dom/issues/744.

The assumption here is an early return for DocumentFragment that has a host by adoptNode() and that adoption generally doesn't affect DocumentFragment otherwise (only its children).

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

Ran 13 Firefox configurations based on mozilla-central, and Chrome, and Safari on GitHub CI

Total 3 tests and 2 subtests

Status Summary

Firefox

OK : 3
PASS: 61
FAIL: 18

Chrome

OK : 3
PASS: 77
FAIL: 2

Safari

OK : 3
PASS: 77
FAIL: 2

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/dom/nodes/adoption.window.html
appendChild() and DocumentFragment: FAIL (Chrome: PASS, Safari: PASS)
appendChild() and ShadowRoot: FAIL (Chrome: PASS, Safari: PASS)
adoptNode() and DocumentFragment with host: FAIL (Chrome: FAIL, Safari: FAIL)
appendChild() and DocumentFragment with host: FAIL (Chrome: PASS, Safari: PASS)
/custom-elements/adopted-callback.html
Moving the <template>'s content of a custom element from the owner document into an HTML document fetched by XHR must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the <template>'s content of a custom element from the owner document into the document of an iframe must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into a cloned document must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into an HTML document fetched by XHR must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into a document created by createHTMLDocument must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the <template>'s content of a custom element from the owner document into a new document must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into an HTML document created by createDocument must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the <template>'s content of a custom element from the owner document into a cloned document must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the <template>'s content of a custom element from the owner document into a document created by createHTMLDocument must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into the document of the template elements must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into the document of an iframe must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the shadow host's shadow of a custom element from the owner document into a new document must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
Moving the <template>'s content of a custom element from the owner document into an HTML document created by createDocument must enqueue and invoke adoptedCallback: FAIL (Chrome: PASS, Safari: PASS)
/html/semantics/scripting-1/the-template-element/template-element/template-content-hierarcy.html
Template content should throw exception when its ancestor in a different document but connected via host is being append.: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/766599c3407c [wpt PR 16348] - Adoption and DocumentFragment, a=testonly https://hg.mozilla.org/integration/autoland/rev/52069e81a717 [wpt PR 16348] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.