Closed Bug 1858247 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42465 - Add AttributePart imperative API support

Categories

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

task

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Mason Freed <masonf@chromium.org> wrote:

Add AttributePart imperative API support

See the explainer [1] for details, but this is the start of adding
AttributePart support. This CL adds imperative support for constructing
an AttributePart:

new AttributePart(root,target,localName,automatic,options);

For now, only HTML namespace attributes are supported, as there aren't
prefix or namespaceURI parameters. The automatic parameter controls
whether or not the new Part is listed in the return value for
getParts(). (Automatic parts are not returned.)

[1] https://docs.google.com/document/d/1z0YCj06-LFTWJlR_ayhtCOV2O4cJ5W1fHZbfckFsOdU/edit

Bug: 1453291
Change-Id: Ib1f4b31b282f707280fb9da1208c8ea3e3e08f03
Reviewed-on: https://chromium-review.googlesource.com/4927874
WPT-Export-Revision: 54ebca545740ecb30b096e90649735ccc44b3536

PR 42465 applied with additional changes from upstream: 4e64b646662678a6ba01e7fd5847fd8bdbf47fb2
Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 1 tests and 20 subtests

Status Summary

Firefox

OK : 1
FAIL: 20

Chrome

OK : 1
PASS: 16
FAIL: 4

Safari

OK : 1
FAIL: 20

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /dom/parts/basic-dom-part-objects.tentative.html [wpt.fyi]
    • Basic imperative DOM Parts object construction (Document): FAIL (Chrome: FAIL, Safari: FAIL)
    • Cloning (Document): FAIL (Chrome: FAIL, Safari: FAIL)
    • Cloning Element (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning Text (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning Comment (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning CDATASection (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning ProcessingInstruction (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • DOM mutations are not tracked (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • ChildNodePart children manipulation (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Corner case ChildNodePart construction and cloning (Document): FAIL (Chrome: PASS, Safari: FAIL)
    • Basic imperative DOM Parts object construction (DocumentFragment): FAIL (Chrome: FAIL, Safari: FAIL)
    • Cloning (DocumentFragment): FAIL (Chrome: FAIL, Safari: FAIL)
    • Cloning Element (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning Text (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning Comment (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning CDATASection (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • Cloning ProcessingInstruction (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • DOM mutations are not tracked (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • ChildNodePart children manipulation (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
    • Corner case ChildNodePart construction and cloning (DocumentFragment): FAIL (Chrome: PASS, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4d1e1cc46d75 [wpt PR 42465] - Add AttributePart imperative API support, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.