Skip to content

Fix upgrade particular elements within a document again #11261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2025

Conversation

annevk
Copy link
Member

@annevk annevk commented Apr 25, 2025

When a CustomElementRegistry define() call starts upgrading elements, we need to make sure to only include those associated with the current registry.

This has test coverage through WPT custom-elements/registries/CustomElementRegistry-upgrade.html.

Fixes #11256.


/custom-elements.html ( diff )

When a CustomElementRegistry define() call starts upgrading elements, we need to make sure to only include those associated with the current registry.

This has test coverage through WPT custom-elements/registries/CustomElementRegistry-upgrade.html.

Fixes #11256.
@annevk annevk added the topic: custom elements Relates to custom elements (as defined in DOM and HTML) label Apr 25, 2025
@annevk annevk requested a review from domenic April 28, 2025 08:17
@annevk annevk merged commit 5f9f41b into main Apr 28, 2025
2 checks passed
@annevk annevk deleted the annevk/define-upgrade-scoping branch April 28, 2025 11:35
@AtkinsSJ
Copy link
Contributor

I tried this out earlier this morning and it definitely helps a lot! I'm still getting some problems but I don't have time to investigate right now. I'll open other issues once I do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: custom elements Relates to custom elements (as defined in DOM and HTML)
Development

Successfully merging this pull request may close these issues.

Agent's active custom element constructor map can have null registries, causing problems
3 participants