[wpt-sync] Sync PR 56176 - Move scoped custom element registry for createElement and attachShadow
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox147 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 56176 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/56176
Details from upstream follow.
Ryosuke Niwa <rniwa@webkit.org> wrote:
Move scoped custom element registry for createElement and attachShadow
Also add a test case for specifying null custom element registry in an ancestor element.
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
CI Results
Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 36 tests and 1975 subtests
Status Summary
Firefox
OK : 3[GitHub] 32[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-24h2-debug, Gecko-windows11-32-24h2-opt, Gecko-windows11-64-24h2-debug, Gecko-windows11-64-24h2-opt]
PASS : 2070
FAIL : 28[GitHub] 183[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-24h2-debug, Gecko-windows11-32-24h2-opt, Gecko-windows11-64-24h2-debug, Gecko-windows11-64-24h2-opt]
ERROR: 2[GitHub] 4[Gecko-android-em-14-x86_64-debug-geckoview, Gecko-android-em-14-x86_64-lite-opt-geckoview, Gecko-android-em-14-x86_64-opt-geckoview, Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-32-24h2-debug, Gecko-windows11-32-24h2-opt, Gecko-windows11-64-24h2-debug, Gecko-windows11-64-24h2-opt]
Chrome
OK : 3
FAIL : 28
ERROR: 2
Safari
OK : 5
PASS : 27
FAIL : 21
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /custom-elements/registries/Construct.html [wpt.fyi]
- A constructor with only a scoped custom element registry definition should fail upon construction:
FAIL - A constructor uses the global registry to create an element:
FAIL - A constructor creating an element from another registry before or after super call should work:
FAIL
- A constructor with only a scoped custom element registry definition should fail upon construction:
- /custom-elements/registries/CustomElementRegistry-define.html [wpt.fyi]
- Create a CustomElementRegistry not identically equal to window.customElements:
FAIL - Defining an element in the global registry does not add a definition to a scoped CustomElementRegistry:
FAIL - Defining an element in a scoped global registry does not add a definition to the global registry:
FAIL
- Create a CustomElementRegistry not identically equal to window.customElements:
- /custom-elements/registries/CustomElementRegistry-initialize.html [wpt.fyi]
- initialize is a function on both global and scoped CustomElementRegistry:
FAIL - initialize sets element.customElementRegistry to the global registry:
FAIL - initialize does not set the registry of nested shadow tree to the global registry:
FAIL - initialize sets element.customElementRegistry to a scoped registry:
FAIL - initialize does not set the registry of nested shadow tree to a scoped registry:
FAIL - initialize sets element.customElementRegistry permantently:
FAIL - initialize is no-op on a subtree with a non-null registry:
FAIL - initialize works on Document:
FAIL - initialize works on DocumentFragment:
FAIL
- initialize is a function on both global and scoped CustomElementRegistry:
- /custom-elements/registries/CustomElementRegistry-multi-register.html [wpt.fyi]
- Same constructor can be registered to different registries:
FAIL - Non-global registries still reject duplicate registrations of the same constructor:
FAIL
- Same constructor can be registered to different registries:
- /custom-elements/registries/CustomElementRegistry-upgrade.html [wpt.fyi]
- upgrade is a function on both global and scoped CustomElementRegistry:
FAIL - upgrade is a no-op when called on a shadow root with no association:
FAIL - upgrade should upgrade a candidate element when called on a shadow root with an association:
FAIL - upgrade should not upgrade a candidate element not associated with a registry:
FAIL
- upgrade is a function on both global and scoped CustomElementRegistry:
- /custom-elements/registries/Document-createElement.html [wpt.fyi]:
ERROR(Chrome:ERROR, Safari:OK) - /custom-elements/registries/Document-createElementNS.html [wpt.fyi]:
ERROR(Chrome:ERROR, Safari:OK) - /custom-elements/registries/Document-customElementRegistry.html [wpt.fyi]
- customElementRegistry on a document should return window.customElements by default:
FAIL - customElementRegistry on a document without a browsing context should return null:
FAIL - customElementRegistry on a document of a connected iframe should return contentWindow.customElements:
FAIL - customElementRegistry on a document of a disconnected iframe should return contentWindow.customElements:
FAIL
- customElementRegistry on a document should return window.customElements by default:
- /custom-elements/registries/Document-importNode-cross-document.window.html [wpt.fyi]
- Cloning with global registry:
FAIL - Cloning with explicit global registry:
FAIL - Cloning with scoped registry:
FAIL - Cloning including shadow tree with global registry:
FAIL - Cloning including shadow tree with explicit global registry:
FAIL - Cloning including shadow tree with scoped registry:
FAIL - Cloning with global registry (null registry target):
FAIL - Cloning with explicit global registry (null registry target):
FAIL - Cloning with scoped registry (null registry target):
FAIL - Cloning including shadow tree with global registry (null registry target):
FAIL - Cloning including shadow tree with explicit global registry (null registry target):
FAIL - Cloning including shadow tree with scoped registry (null registry target):
FAIL
- Cloning with global registry:
- /custom-elements/registries/Document-importNode.html [wpt.fyi]:
ERROR - /custom-elements/registries/Element-customElementRegistry-exceptions.html [wpt.fyi]
- customElementRegistry on a failed custom element created by calling createElement on CustomElementRegistry should return the registry:
FAIL - customElementRegistry on a failed custom element created by setting innerHTML should return the associated scoped registry:
FAIL - customElementRegistry on a failed custom element created by parser should return the specified custom regsitry:
FAIL
- customElementRegistry on a failed custom element created by calling createElement on CustomElementRegistry should return the registry:
- /custom-elements/registries/Element-customElementRegistry.html [wpt.fyi]
- customElementRegistry on a newly constrcuted element should return window.customElements by default:
FAIL - customElementRegistry on an element inside a declarative shadow DOM should return window.customElements by default:
FAIL - customElementRegistry on an element inside a declarative shadow DOM with shadowrootcustomelementregistry should return null:
FAIL - customElementRegistry on a clone of a declarative shadow tree with shadowrootcustomelementregistry should return null:
FAIL - customElementRegistry on a clone of a declarative shadow tree with shadowrootcustomelementregistry should return the global registry after getting inserted into a document:
FAIL - customElementRegistry on an element inside a declarative shadow DOM with shadowrootcustomelementregistry should return the scoped registry after calling initialize:
FAIL - customElementRegistry on a builtin element created by calling createElement on CustomElementRegistry should return the registry:
FAIL - customElementRegistry on an upgarde candidate created by calling createElement on CustomElementRegistry should return the registry:
FAIL - customElementRegistry on an unknown element created by calling createElement on CustomElementRegistry should return the registry:
FAIL - customElementRegistry on a defined custom element created by calling createElement on CustomElementRegistry should return the registry:
FAIL
- customElementRegistry on a newly constrcuted element should return window.customElements by default:
- /custom-elements/registries/Element-innerHTML.html [wpt.fyi]
- innerHTML on a disconnected element should use the scoped registry it was created with:
FAIL - nested descendants in innerHTML on a disconnected element should use the scoped registry the element was created with:
FAIL - innerHTML on a disconnected element should use the scoped registry it was created with when parsing a simple HTML:
FAIL - innerHTML on an inserted element should continue to use the scoped registry it was created with:
FAIL - nested descendants in innerHTML should use the null registry when the container element has null registry:
FAIL - insertAdjacentHTML should use the element's registry even when the registry is null:
FAIL
- innerHTML on a disconnected element should use the scoped registry it was created with:
- /custom-elements/registries/ShadowRoot-init-customElementRegistry.html [wpt.fyi]
- A newly attached disconnected ShadowRoot should use the global registry by default:
FAIL(Chrome:FAIL, Safari:PASS) - A newly attached connected ShadowRoot should use the global registry by default:
FAIL(Chrome:FAIL, Safari:PASS) - A newly attached disconnected ShadowRoot should use the scoped registry if explicitly specified in attachShadow:
FAIL(Chrome:FAIL, Safari:PASS) - A newly attached connected ShadowRoot should use the scoped registry if explicitly specified in attachShadow:
FAIL(Chrome:FAIL, Safari:PASS) - attachShadow() should use null registry when customElementRegistry is null (host uses global registry):
FAIL(Chrome:FAIL, Safari:FAIL) - attachShadow() should use null registry when customElementRegistry is null (host uses custom registry):
FAIL(Chrome:FAIL, Safari:FAIL) - attchShadow on a builtin element with null customElementRegistry should create a ShadowRoot with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - attchShadow on a custom elememnt candidate with null customElementRegistry should create a ShadowRoot with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - attchShadow on a custom elememnt with null customElementRegistry should create a ShadowRoot with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - attachShadow() should use the null registry when the shadow host uses null registry and customElementRegistry is null:
FAIL(Chrome:FAIL, Safari:PASS)
- A newly attached disconnected ShadowRoot should use the global registry by default:
- /custom-elements/registries/ShadowRoot-init-declarative.html [wpt.fyi]
- Custom element inside 'shadowrootcustomelementregistry' declarative shadow root:
FAIL - Built-in element inside 'shadowrootcustomelementregistry' declarative shadow root:
FAIL
- Custom element inside 'shadowrootcustomelementregistry' declarative shadow root:
- /custom-elements/registries/ShadowRoot-innerHTML.html [wpt.fyi]
- innerHTML on a shadow root should use the scoped registry:
FAIL - innerHTML on a connected shadow root should use the associated scoped registry:
FAIL - innerHTML on a connected shadow root should not upgrade a custom element inside a template element:
FAIL - innerHTML on a connected shadow root should be able to create an unknown element:
FAIL
- innerHTML on a shadow root should use the scoped registry:
- /custom-elements/registries/adoption.window.html [wpt.fyi]
- Adoption with global registry:
FAIL - Adoption with explicit global registry:
FAIL - Adoption with scoped registry:
FAIL - Adoption with global registry into a scoped registry:
FAIL - Adoption with explicit global registry into a scoped registry:
FAIL - Adoption with scoped registry into a scoped registry:
FAIL - Adoption including shadow root with global registry:
FAIL - Adoption including shadow root with explicit global registry:
FAIL - Adoption including shadow root with scoped registry:
FAIL - Adoption including shadow root with global registry into a scoped registry:
FAIL - Adoption including shadow root with explicit global registry into a scoped registry:
FAIL - Adoption including shadow root with scoped registry into a scoped registry:
FAIL - Adoption with global registry (null registry target):
FAIL - Adoption with explicit global registry (null registry target):
FAIL - Adoption with scoped registry (null registry target):
FAIL - Adoption with global registry into a scoped registry (null registry target):
FAIL - Adoption with explicit global registry into a scoped registry (null registry target):
FAIL - Adoption with scoped registry into a scoped registry (null registry target):
FAIL - Adoption including shadow root with global registry (null registry target):
FAIL - Adoption including shadow root with explicit global registry (null registry target):
FAIL - Adoption including shadow root with scoped registry (null registry target):
FAIL - Adoption including shadow root with global registry into a scoped registry (null registry target):
FAIL - Adoption including shadow root with explicit global registry into a scoped registry (null registry target):
FAIL - Adoption including shadow root with scoped registry into a scoped registry (null registry target):
FAIL - Adoption with global registry (scoped registry target):
FAIL - Adoption with explicit global registry (scoped registry target):
FAIL - Adoption with scoped registry (scoped registry target):
FAIL - Adoption with global registry into a scoped registry (scoped registry target):
FAIL - Adoption with explicit global registry into a scoped registry (scoped registry target):
FAIL - Adoption with scoped registry into a scoped registry (scoped registry target):
FAIL - Adoption including shadow root with global registry (scoped registry target):
FAIL - Adoption including shadow root with explicit global registry (scoped registry target):
FAIL - Adoption including shadow root with scoped registry (scoped registry target):
FAIL - Adoption including shadow root with global registry into a scoped registry (scoped registry target):
FAIL - Adoption including shadow root with explicit global registry into a scoped registry (scoped registry target):
FAIL - Adoption including shadow root with scoped registry into a scoped registry (scoped registry target):
FAIL
- Adoption with global registry:
- /custom-elements/registries/constructor-reentry-with-different-definition.html [wpt.fyi]
- Re-entry via upgrade before calling super():
FAIL - Re-entry via upgrade after calling super():
FAIL - Re-entry via direct constructor call before calling super():
FAIL - Re-entry via direct constructor call after calling super():
FAIL
- Re-entry via upgrade before calling super():
- /custom-elements/registries/element-mutation.html [wpt.fyi]
- An element with global registry should not change its registry when moved into a shadow tree with scoped registry.:
FAIL - An element with scoped registry should not change its registry when moved out of the shadow tree.:
FAIL - An element with scoped registry should not change its registry when moved into another shadow tree with different scoped registry.:
FAIL
- An element with global registry should not change its registry when moved into a shadow tree with scoped registry.:
- /custom-elements/registries/global.window.html [wpt.fyi]
- initialize() of global registry should throw for nodes from another document:
FAIL - createElement() should throw with global registry from another document:
FAIL - createElementNS() should throw with global registry from another document:
FAIL - attachShadow() should throw with global registry from another document:
FAIL - importNode() should throw with global registry from another document:
FAIL
- initialize() of global registry should throw for nodes from another document:
- /custom-elements/registries/initial-about-blank.window.html [wpt.fyi]
- Each navigable document has its own registry:
FAIL
- Each navigable document has its own registry:
- /custom-elements/registries/pseudo-class-defined.window.html [wpt.fyi]
- "uncustomized" :defined doesn't care about your registry':
FAIL - "custom" :defined doesn't care about your registry:
FAIL - "custom" :defined should apply after initialize:
FAIL
- "uncustomized" :defined doesn't care about your registry':
- /custom-elements/registries/scoped-custom-element-registry-customelementregistry-attribute-in-xhtml.xhtml [wpt.fyi]
- XHTML parser should create a custom element candidate with null registry if customelementregistry is set:
FAIL - XHTML parser should create a defined custom element with null registry if customelementregistry is set:
FAIL - XHTML fragment parser should create a custom element candidate with null registry if customelementregistry is set:
FAIL - XHTML fragment parser should create a defined custom element with null registry if customelementregistry is set:
FAIL
- XHTML parser should create a custom element candidate with null registry if customelementregistry is set:
- /custom-elements/registries/scoped-custom-element-registry-customelementregistry-attribute.html [wpt.fyi]
- HTML parser should create a builtin element with null registry if customelementregistry is set:
FAIL(Chrome:FAIL, Safari:FAIL) - Setting customelementregistry content attribute after a builtin element had finishsed parsing should not set null registry:
FAIL(Chrome:FAIL, Safari:PASS) - Cloning a builtin element with null regsitry should create an element with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - HTML parser should create a custom element candidate with null registry if customelementregistry is set:
FAIL(Chrome:FAIL, Safari:FAIL) - Setting customelementregistry content attribute after a custom element candidate had finishsed parsing should not set null registry:
FAIL(Chrome:FAIL, Safari:PASS) - Cloning a custom element candidate with null regsitry should create an element with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - HTML parser should create a custom element with null registry if customelementregistry is set:
FAIL(Chrome:FAIL, Safari:FAIL) - Setting customelementregistry content attribute after a custom element had finishsed parsing should not set null registry:
FAIL(Chrome:FAIL, Safari:PASS) - Cloning a custom element with null regsitry should create an element with null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - Descendants of an element with customelementregistry should use null registry:
FAIL(Chrome:FAIL, Safari:FAIL) - Setting customelementregistry content attribute during constructor should not make it use null registry:
FAIL(Chrome:FAIL, Safari:PASS)
- HTML parser should create a builtin element with null registry if customelementregistry is set:
- /custom-elements/registries/scoped-registry-append-does-not-upgrade.html [wpt.fyi]
- customElementRegistry of an upgrade candidate created in a document without a browsing context uses null regsitry by default:
FAIL(Chrome:FAIL, Safari:PASS) - Connecting a custom element candiate in a shadow root with a scoped custom element registry has null registry by default:
FAIL(Chrome:FAIL, Safari:PASS) - Connecting a custom element candiate with null registry does not set the registry:
FAIL(Chrome:FAIL, Safari:FAIL) - Connecting a custom element candiate with a scoped custom element registry does not change the registry:
FAIL(Chrome:FAIL, Safari:PASS) - Inserting a custom element candiate with null registry does not change the registry:
FAIL(Chrome:FAIL, Safari:FAIL) - Inserting the shadow host of a shadow root with a scoped custom element registry does not change the registry:
FAIL(Chrome:FAIL, Safari:PASS) - Inserting a node from another document results in the custom element registry to be set and upgraded.:
FAIL(Chrome:FAIL, Safari:FAIL)
- customElementRegistry of an upgrade candidate created in a document without a browsing context uses null regsitry by default:
- /custom-elements/registries/scoped-registry-define-upgrade-criteria.html [wpt.fyi]
- Adding definition to global registry should not affect shadow roots using scoped registry:
FAIL - Adding definition to scoped registry should affect all associated shadow roots:
FAIL - Adding definition to scoped registry should not affect document tree scope:
FAIL - Adding definition to scoped registry should not affect shadow roots using other registries:
FAIL - Adding definition to global registry should upgrade nodes even after the node is moved into a separate shadow tree.:
FAIL - Adding definition to scoped registry should upgrade nodes even after the node is moved to a separate shadow tree using a different registry.:
FAIL - Adding definition to scoped registry affects associated shadow roots in all iframes:
FAIL - Adding definition to scoped registry affects associated shadow roots in other frame trees:
FAIL - Adding definition to scoped registry should not upgrade disconnected elements:
FAIL - Adding definition to scoped registry should not upgrade nodes in constructed documents:
FAIL - Adding definition to scoped registry should not upgrade nodes in detached frames:
FAIL
- Adding definition to global registry should not affect shadow roots using scoped registry:
- /custom-elements/registries/scoped-registry-define-upgrade-order.html [wpt.fyi]
- Upgrade in tree order in the same tree scope:
FAIL - Upgrade in shadow-including tree order across tree scopes:
FAIL - Upgrade order does not depend on shadow root attach order:
FAIL - Upgrade in association order across documents, then tree order in each document:
FAIL - Upgrade order is not affected by DOM order between child frames:
FAIL - Upgrade order is affected by shadow tree adoption across documents:
FAIL - Elements in the "owner" window of a scoped registry are not always upgraded first:
FAIL
- Upgrade in tree order in the same tree scope:
- /custom-elements/registries/scoped-registry-initialize-upgrades.html [wpt.fyi]
- Document: customElementRegistry.prototype.initialize should upgrade the element given to the first argument:
FAIL - Document: customElementRegistry.prototype.initialize should upgrade elements in tree order:
FAIL - Document: customElementRegistry.prototype.initialize only upgrades elements beloning to the registry:
FAIL - HTMLDocument: customElementRegistry.prototype.initialize should upgrade the element given to the first argument:
FAIL - HTMLDocument: customElementRegistry.prototype.initialize should upgrade elements in tree order:
FAIL - HTMLDocument: customElementRegistry.prototype.initialize only upgrades elements beloning to the registry:
FAIL - XHTMLDocument: customElementRegistry.prototype.initialize should upgrade the element given to the first argument:
FAIL - XHTMLDocument: customElementRegistry.prototype.initialize should upgrade elements in tree order:
FAIL - XHTMLDocument: customElementRegistry.prototype.initialize only upgrades elements beloning to the registry:
FAIL
- Document: customElementRegistry.prototype.initialize should upgrade the element given to the first argument:
- /custom-elements/registries/scoped-registry-initialize.html [wpt.fyi]:
ERROR - /custom-elements/registries/scoped-registry-registry-define-get-etc.html [wpt.fyi]
- Custom element registries with a registered custom element return the class in their get method, and the name in their getName method:
FAIL - Scoped Custom element registries do not inherit names or classes from the global registry:
FAIL - Scoped Custom element registries return the same constructor when it is defined in both:
FAIL - Scoped Custom element registries allow registering name that exists in global registry:
FAIL - Custom element registries with a registered custom element resolve the class in their whenDefined method:
FAIL - Scoped Custom element registries resolve the same constructor from whenDefined when it is defined in both:
FAIL - Scoped Custom element registry getters do not resolve globally registered classes from whenDefined:
FAIL
- Custom element registries with a registered custom element return the class in their get method, and the name in their getName method:
- /custom-elements/registries/template.window.html [wpt.fyi]
- shadowRootCustomElementRegistry reflects as string:
FAIL - Serializing a ShadowRoot with a null registry:
FAIL - Serializing a ShadowRoot with a registry that differs from its host:
FAIL
- shadowRootCustomElementRegistry reflects as string:
Comment 5•11 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/92543c58c310
https://hg.mozilla.org/mozilla-central/rev/80beb295e1d2
Description
•