Bug 307920
| Summary: | Incorrect customElementRegistry when using importNode to create elements | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Orvell <steveorvell> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | rniwa |
| Priority: | P2 | ||
| Version: | Safari Technology Preview | ||
| Hardware: | Mac (Apple Silicon) | ||
| OS: | iOS 26 | ||
| Bug Depends on: | |||
| Bug Blocks: | 154907 | ||
Steve Orvell
When `document.importNode` is used to create elements that have a null registry, the resulting elements have an incorrect registry when importNode does not specify a registry. This should create elements with `customElementRegistry` set to the document default registry (e.g. window.customElements), but instead it is set to `undefined`, which incorrect and an invalid value.
See reproduction (asserts in console): https://codepen.io/Steve-Orvell/pen/MYeRmQM?editors=0010
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |