Skip to content

[scoped-registry] Null registry element should get registry on adopt instead of insert#57213

Merged
chromium-wpt-export-bot merged 1 commit into
masterfrom
chromium-export-cl-7078864
Jan 27, 2026
Merged

[scoped-registry] Null registry element should get registry on adopt instead of insert#57213
chromium-wpt-export-bot merged 1 commit into
masterfrom
chromium-export-cl-7078864

Conversation

@chromium-wpt-export-bot

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 16, 2026

Copy link
Copy Markdown
Collaborator

It was discussed over TPAC and outlined in
whatwg/dom#1423 that we want to set registry on
null registry element during adoption instead of insertion of a node.

Bug: 448853877
Change-Id: I63b8a7bcef98ead66bd1375c9b1df69d9b9bd597
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7078864
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Jayson Chen <jaysonchen@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1574942}

instead of insert

It was discussed over TPAC and outlined in
whatwg/dom#1423 that we want to set registry on
null registry element during adoption instead of insertion of a node.

Bug: 448853877
Change-Id: I63b8a7bcef98ead66bd1375c9b1df69d9b9bd597
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7078864
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Commit-Queue: Jayson Chen <jaysonchen@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1574942}

@wpt-pr-bot wpt-pr-bot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot
chromium-wpt-export-bot merged commit 5b0c22e into master Jan 27, 2026
19 checks passed
@chromium-wpt-export-bot
chromium-wpt-export-bot deleted the chromium-export-cl-7078864 branch January 27, 2026 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants