Closed Bug 2028455 Opened 3 months ago Closed 2 months ago

[wpt-sync] Sync PR 58892 - [Platform-provided behaviors] Introduce HTMLSubmitButtonBehavior

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
151 Branch
Tracking Flags:
Tracking Status
firefox151 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Ana Sollano Kim <ansollan@microsoft.com> wrote:

[Platform-provided behaviors] Introduce HTMLSubmitButtonBehavior

This change introduces the HTMLSubmitButtonBehavior interface, which
will allow custom elements to adopt submit button functionality and
attribute handling by attaching this behavior via ElementInternals.

In this CL, ElementInternals is updated to validate behavior attachment,
preventing duplicate behavior types or the reuse of behavior instances
across multiple elements. Property delegation for form association and
labeling and support for standard attributes is added to
HTMLSubmitButtonBehavior as well. Upcoming CLs will implement form
submission logic.

Explainer:
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PlatformProvidedBehaviors/explainer.md
Design doc:
https://docs.google.com/document/d/1LA1hhzxmi4OmZoGtIdnwvL3g7y48YjXTOoUvFtxFugE/edit?usp=sharing

Bug: 486928684
Change-Id: I9047177bf30a9a6615ee506735a120be6f671fb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7693458
Reviewed-by: Dan Clark \<daniec@microsoft.com>
Reviewed-by: Mason Freed \<masonf@chromium.org>
Commit-Queue: Ana Sollano Kim \<ansollan@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1608078}

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

CI Results

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

Total 183 tests

Status Summary

Firefox

OK : 1[GitHub] 175[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 : 1[GitHub] 3[Gecko-linux2204-64-wayland-debug, Gecko-linux2204-64-wayland-opt] 3913[Gecko-windows11-32-24h2-debug, Gecko-windows11-32-24h2-opt] 3916[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-64-24h2-debug, Gecko-windows11-64-24h2-opt]
FAIL : 13[GitHub] 231[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] 233[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]
ERROR: 1[GitHub] 2[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 : 1
PASS : 8
FAIL : 6
ERROR: 1

Safari

OK : 1
PASS : 1
FAIL : 13
ERROR: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /custom-elements/Document-createElement.html [wpt.fyi]
    • document.createElement must report a NotSupportedError when the element is adopted into a the document of an iframe during construction: FAIL
    • document.createElement must report a NotSupportedError when the element is inserted into a the document of an iframe during construction: FAIL
    • document.createElement must not report a NotSupportedError when the element is adopted back from a the document of an iframe during construction: FAIL
  • /custom-elements/cross-realm-callback-report-exception.html [wpt.fyi]
    • constructor: FAIL
  • /custom-elements/element-internals-aria-element-reflection.html [wpt.fyi]
    • Setting ariaLabelledByElements on ElementInternals should change the accessible name of the custom element: FAIL
    • Setting aria-labelledby or ariaLabelledByElements on the custom element should supersede the value of ariaLabelledByElements on ElementInternals: FAIL
  • /custom-elements/element-internals-behaviors.tentative.html [wpt.fyi]
    • behaviors returns empty array when no behaviors configured: FAIL (Chrome: PASS, Safari: FAIL)
    • behaviors is a read-only frozen array: FAIL (Chrome: FAIL, Safari: FAIL)
    • behaviors array cannot be modified after attachment: FAIL (Chrome: FAIL, Safari: FAIL)
    • attachInternals throws TypeError for duplicate behavior instance: FAIL (Chrome: FAIL, Safari: FAIL)
    • attachInternals throws TypeError for multiple instances of same behavior type: FAIL (Chrome: FAIL, Safari: FAIL)
    • attachInternals throws TypeError when behavior is already attached to another element: FAIL (Chrome: FAIL, Safari: FAIL)
    • attachInternals throws TypeError for string in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • attachInternals throws TypeError for null in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • attachInternals throws TypeError for undefined in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • attachInternals throws TypeError for plain object in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • attachInternals throws TypeError for number in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • attachInternals throws TypeError for DOM element in behaviors array: FAIL (Chrome: PASS, Safari: FAIL)
    • Behavior state is preserved across disconnect and reconnect: FAIL (Chrome: FAIL, Safari: FAIL)
  • /custom-elements/form-associated/ElementInternals-submit-behavior.tentative.html [wpt.fyi]: ERROR (Chrome: ERROR, Safari: ERROR)
  • /custom-elements/reactions/AriaMixin-element-attributes.html [wpt.fyi]
    • ariaControlsElements in Element must enqueue an attributeChanged reaction when adding aria-controls content attribute: FAIL
    • ariaControlsElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaDescribedByElements in Element must enqueue an attributeChanged reaction when adding aria-describedby content attribute: FAIL
    • ariaDescribedByElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaDetailsElements in Element must enqueue an attributeChanged reaction when adding aria-details content attribute: FAIL
    • ariaDetailsElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaErrorMessageElements in Element must enqueue an attributeChanged reaction when adding aria-errormessage content attribute: FAIL
    • ariaErrorMessageElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaFlowToElements in Element must enqueue an attributeChanged reaction when adding aria-flowto content attribute: FAIL
    • ariaFlowToElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaLabelledByElements in Element must enqueue an attributeChanged reaction when adding aria-labelledby content attribute: FAIL
    • ariaLabelledByElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
    • ariaOwnsElements in Element must enqueue an attributeChanged reaction when adding aria-owns content attribute: FAIL
    • ariaOwnsElements in Element must enqueue an attributeChanged reaction when replacing an existing attribute: FAIL
  • /custom-elements/registries/Construct.html [wpt.fyi]
    • A constructor creating an element from another registry before or after super call should work: FAIL
  • /custom-elements/registries/CustomElementRegistry-initialize.html [wpt.fyi]
    • initialize throws when the registry scoped is false and the root is the document.: FAIL
    • initialize throws when the registry scoped is false and the root document already has another registry: FAIL
    • 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 descendants whose customElementRegistry already uses a different 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 sets registry on shadow root descendants with no registry: FAIL
  • /custom-elements/registries/CustomElementRegistry-upgrade.html [wpt.fyi]
    • upgrade is a no-op when called on a shadow root with no association: FAIL
    • upgrade is a no-op when called on an element associated with a different registry: 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
  • /custom-elements/registries/Document-createElement.html [wpt.fyi]
    • createElement should use the specified scoped registry: FAIL
    • createElement should create a builtin element regardless of a custom element registry specified: FAIL
    • createElement should create an upgrade candidate when there is no matching definition in the specified registry: FAIL
    • document.createElement should create a builtin element with null registry if customElementRegistry is set to null: FAIL
    • document.createElement should create a custom element candidate with null registry if customElementRegistry is set to null: FAIL
    • document.createElement should create a custom element candidate with null registry if customElementRegistry is set to null even if there is a custom element of the same name in the glboal registry: FAIL
    • createElement should create an upgrade candidate and the candidate should be upgraded when the element is defined: FAIL
    • createElement on a non-HTML document should still handle registries correctly: FAIL
  • /custom-elements/registries/Document-createElementNS.html [wpt.fyi]
    • createElementNS should use the specified scoped registry: FAIL
    • createElementNS should create a builtin element regardless of a custom element registry specified: FAIL
    • createElementNS should create an upgrade candidate when there is no matching definition in the specified registry: FAIL
    • document.createElement should create a builtin element with null registry if customElement is set to null: FAIL
    • document.createElement should create a custom element candidate with null registry if customElement is set to null: FAIL
    • document.createElement should create a defined custom element with null registry if customElement is set to null: FAIL
    • createElementNS should create an upgrade candidate and the candidate should be upgraded when the element is defined: FAIL
    • createElementNS on a non-HTML document should still handle registries correctly: FAIL
  • /custom-elements/registries/Document-customElementRegistry.html [wpt.fyi]
    • customElementRegistry on a document of a disconnected iframe should return contentWindow.customElements: FAIL
  • /custom-elements/registries/Document-importNode-cross-document.window.html [wpt.fyi]
    • Cloning with scoped registry: FAIL
    • Cloning including shadow tree with scoped registry: FAIL
    • Cloning with scoped registry (null registry target): FAIL
    • Cloning including shadow tree with scoped registry (null registry target): FAIL
  • /custom-elements/registries/Document-importNode.html [wpt.fyi]
    • importNode should clone using the specified registry if target's registry is null: FAIL
    • importNode should preserve null-ness of custom element registry: FAIL
    • importNode should clone a shadow host with a declarative shadow DOM using a specified scoped registry: FAIL
    • importNode should clone using target's registry if non-null, including when it's not the global registry: FAIL
    • importNode should clone a template content using a specified scoped registry: FAIL
    • importNode: pass options argument with value { selfOnly: true }: FAIL
    • importNode: pass options argument with value { customElementRegistry: null }: FAIL
  • /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
  • /custom-elements/registries/Element-customElementRegistry.html [wpt.fyi]
    • 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 inside a custom element constructor should return the correct registry: FAIL
  • /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
  • /custom-elements/registries/ShadowRoot-init-customElementRegistry.html [wpt.fyi]
    • A newly attached disconnected ShadowRoot should use the scoped registry if explicitly specified in attachShadow: FAIL
    • A newly attached connected ShadowRoot should use the scoped registry if explicitly specified in attachShadow: FAIL
    • attachShadow() should use null registry when customElementRegistry is null (host uses global registry): FAIL
    • attachShadow() should use null registry when customElementRegistry is null (host uses custom registry): FAIL
    • attchShadow on a builtin element with null customElementRegistry should create a ShadowRoot with null registry: FAIL
    • attchShadow on a custom elememnt candidate with null customElementRegistry should create a ShadowRoot with null registry: FAIL
    • attchShadow on a custom elememnt with null customElementRegistry should create a ShadowRoot with null registry: FAIL
  • /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-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
  • /custom-elements/registries/adoption.window.html [wpt.fyi]
    • 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 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 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 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
  • /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
  • /custom-elements/registries/element-mutation.html [wpt.fyi]
    • An element with scoped registry should not change its registry when run append out of the shadow tree.: FAIL
    • An element with scoped registry should not change its registry when run append into another shadow tree with different scoped registry.: FAIL
    • An element with scoped registry should not change its registry when run appendChild out of the shadow tree.: FAIL
    • An element with scoped registry should not change its registry when run appendChild into another shadow tree with different scoped registry.: FAIL
    • An element with scoped registry should not change its registry when run prepend out of the shadow tree.: FAIL
    • An element with scoped registry should not change its registry when run prepend into another shadow tree with different scoped registry.: FAIL
    • Declarative shadow DOM with shadowrootcustomelementregistry attribute without registry initialized should remain null registry after adoption.: FAIL
  • /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
  • /custom-elements/registries/initial-about-blank.window.html [wpt.fyi]
    • Each navigable document has its own registry: FAIL
  • /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
  • /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
  • /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
    • Cloning a builtin element with null regsitry should create an element with null registry: FAIL
    • HTML parser should create a custom element candidate with null registry if customelementregistry is set: FAIL
    • Cloning a custom element candidate with null regsitry should create an element with null registry: FAIL
    • HTML parser should create a custom element with null registry if customelementregistry is set: FAIL
    • Cloning a custom element with null regsitry should create an element with null registry: FAIL
    • Descendants of an element with customelementregistry should use null registry: FAIL
  • /custom-elements/registries/scoped-registry-append-does-not-upgrade.html [wpt.fyi]
    • Connecting a custom element candiate in a shadow root with a scoped custom element registry has null registry by default: FAIL
    • Connecting a custom element candiate with null registry does not set the registry: FAIL
    • Connecting a custom element candiate with a scoped custom element registry does not change the registry: FAIL
    • Inserting a custom element candiate with null registry does not change the registry: FAIL
    • Inserting the shadow host of a shadow root with a scoped custom element registry does not change the registry: FAIL
  • /custom-elements/registries/scoped-registry-define-upgrade-criteria.html [wpt.fyi]
    • Adding definition to scoped registry should upgrade nodes associated with the registry.: FAIL
    • 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 scoped 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
  • /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
  • /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
    • CustomElementRegistry.prototype.initialize upgrades already initialized elements: FAIL
    • CustomElementRegistry.prototype.initialize upgrades custom elements in declarative shadow root when initialize() runs before define(): FAIL
    • CustomElementRegistry.prototype.initialize upgrades custom elements in imperative shadow root when inserted before define(): FAIL
  • /custom-elements/registries/scoped-registry-initialize.html [wpt.fyi]
    • Document: customElementRegistry of an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • Document: customElementRegistry of an upgrade candidate created with an explicit customElementRegistry argument should return the registry: FAIL
    • Document: customElementRegistry of an unknown element after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • Document: customElementRegistry of an unknown element created with an explicit customElementRegistry argument should return the registry: FAIL
    • Document: customElementRegistry of document and an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • Document: customElementRegistry of an element created after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • HTMLDocument: customElementRegistry of an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • HTMLDocument: customElementRegistry of an upgrade candidate created with an explicit customElementRegistry argument should return the registry: FAIL
    • HTMLDocument: customElementRegistry of an unknown element after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • HTMLDocument: customElementRegistry of an unknown element created with an explicit customElementRegistry argument should return the registry: FAIL
    • HTMLDocument: customElementRegistry of document and an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • HTMLDocument: customElementRegistry of an element created after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of an upgrade candidate created with an explicit customElementRegistry argument should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of an unknown element after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of an unknown element created with an explicit customElementRegistry argument should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of document and an upgrade candidate after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
    • XHTMLDocument: customElementRegistry of an element created after calling CustomElementRegistry.prototype.initialize should return the registry: FAIL
  • /custom-elements/registries/template.window.html [wpt.fyi]
    • shadowRootCustomElementRegistry reflects as string: FAIL
    • Serializing a null registry ShadowRoot with a global registry host (document): FAIL
    • Serializing a scoped registry ShadowRoot with a global registry host (document): FAIL
    • Serializing a scoped registry ShadowRoot with a null registry host (document): FAIL
    • Serializing a null registry ShadowRoot with a scoped registry host (document): FAIL
    • Serializing a scoped registry ShadowRoot with a scoped registry host (document): FAIL
    • A declarative shadow root gets its default registry from its node document: FAIL
  • /custom-elements/upgrading/upgrade-custom-element-error-event.html [wpt.fyi]: ERROR
    • autonomous: exception thrown in constructor is reported to definition's global: FAIL
    • autonomous: exception thrown by spec due to invalid element state is reported to definition's global: FAIL
    • customized built-in: exception thrown in constructor is reported to definition's global: FAIL
    • customized built-in: exception thrown by spec due to not returning the same value is reported to definition's global: FAIL
  • /custom-elements/form-associated/ElementInternals-reportValidity-bubble.html [wpt.fyi]: FAIL [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], PASS [Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-64-24h2-debug, Gecko-windows11-64-24h2-opt]
  • /custom-elements/form-associated/ElementInternals-reportValidity-delegatesFocus.html [wpt.fyi]: FAIL [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], PASS [Gecko-linux2404-64-debug, Gecko-linux2404-64-opt, Gecko-windows11-64-24h2-debug, Gecko-windows11-64-24h2-opt]

https://hg.mozilla.org/mozilla-central/rev/10fba389c317
https://hg.mozilla.org/mozilla-central/rev/b55fc395de5e

Status: NEW → RESOLVED
Closed: 2 months ago
status-firefox151: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
You need to log in before you can comment on or make changes to this bug.