commit 85526621933b5037a1a94cd172a040500ca9c2ec parent f077de62b9a00c09f843342e0ede34161d32d9e4 Author: moz-wptsync-bot <wptsync@mozilla.com> Date: Wed, 3 Dec 2025 10:34:31 +0000 Bug 2002489 [wpt PR 56283] - Update wpt metadata, a=testonly wpt-pr: 56283 wpt-type: metadata Diffstat:
3 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/testing/web-platform/meta/custom-elements/registries/scoped-custom-element-registry-customelementregistry-attribute.html.ini b/testing/web-platform/meta/custom-elements/registries/scoped-custom-element-registry-customelementregistry-attribute.html.ini @@ -31,3 +31,6 @@ [Setting customelementregistry content attribute during constructor should not make it use null registry] expected: FAIL + + [Descendants of an element with customelementregistry should use null registry] + expected: FAIL diff --git a/testing/web-platform/meta/custom-elements/registries/scoped-registry-append-does-not-upgrade.html.ini b/testing/web-platform/meta/custom-elements/registries/scoped-registry-append-does-not-upgrade.html.ini @@ -19,3 +19,9 @@ [Inserting a node from another document results in the custom element registry to be set and upgraded.] expected: FAIL + + [Inserting a node from another document with global registry results in the custom element registry to be set and upgraded.] + expected: FAIL + + [Inserting a node from another document with null registry results in the custom element registry to be set and upgraded.] + expected: FAIL diff --git a/testing/web-platform/meta/custom-elements/registries/scoped-registry-define-upgrade-criteria.html.ini b/testing/web-platform/meta/custom-elements/registries/scoped-registry-define-upgrade-criteria.html.ini @@ -31,3 +31,6 @@ [Adding definition to scoped registry should upgrade nodes even after the node is moved to a separate shadow tree using a different registry.] expected: FAIL + + [Adding definition to scoped registry should upgrade nodes even after the node is moved into a separate shadow tree.] + expected: FAIL