tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit 9cda45439e518f453bbfcd5b750611c42ba30002
parent 32c704ad26f365712ad0d1e808da91fbea340b59
Author: moz-wptsync-bot <wptsync@mozilla.com>
Date:   Fri, 17 Oct 2025 09:43:43 +0000

Bug 1994943 [wpt PR 55367] - Update wpt metadata, a=testonly

wpt-pr: 55367
wpt-type: metadata

Diffstat:
Atesting/web-platform/meta/custom-elements/registries/element-mutation.html.ini | 9+++++++++
Mtesting/web-platform/meta/custom-elements/registries/scoped-registry-define-upgrade-criteria.html.ini | 6++++++
2 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/testing/web-platform/meta/custom-elements/registries/element-mutation.html.ini b/testing/web-platform/meta/custom-elements/registries/element-mutation.html.ini @@ -0,0 +1,9 @@ +[element-mutation.html] + [An element with global registry should not change its registry when moved into a shadow tree with scoped registry.] + expected: FAIL + + [An element with scoped registry should not change its registry when moved out of the shadow tree.] + expected: FAIL + + [An element with scoped registry should not change its registry when moved into another shadow tree with different scoped registry.] + 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,9 @@ [Adding definition to scoped registry should not upgrade nodes in detached frames] expected: FAIL + + [Adding definition to global registry should upgrade nodes even after the node is moved into a separate shadow tree.] + expected: FAIL + + [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