Skip to content

Introduce keep custom element registry null for elements - #1500

Open
ja-y-son wants to merge 4 commits into
whatwg:mainfrom
ja-y-son:element-keep-custom-element-registry-null
Open

ja-y-son wants to merge 4 commits into
whatwg:mainfrom
ja-y-son:element-keep-custom-element-registry-null

Conversation

@ja-y-son

@ja-y-son ja-y-son commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Introduce an element-level keep custom element registry null flag so HTML can preserve intentionally null custom element registries through cloning and adoption.

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

Jayson Chen added 3 commits August 26, 2026 15:34
Preserve intentionally null element registries during cloning and adoption.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 3f70b8c0-52a8-4e9e-a5a9-a8d2a1b8e925
Do not propagate a fallback registry into descendants of an element whose null registry is intentionally preserved.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 3f70b8c0-52a8-4e9e-a5a9-a8d2a1b8e925
Only preserve a null fallback boundary while the flagged element itself still has a null custom element registry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 3f70b8c0-52a8-4e9e-a5a9-a8d2a1b8e925
Keep the associated value definition concise and move cloning and adoption rationale into the adjacent note.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 3f70b8c0-52a8-4e9e-a5a9-a8d2a1b8e925
@annevk annevk added the do not merge yet Pull request must not be merged per rationale in comment label Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge yet Pull request must not be merged per rationale in comment

Development

Successfully merging this pull request may close these issues.

2 participants