Bug 299603
| Summary: | elements created via parsing can customize with a null registry | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Steve Orvell <steveorvell> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, annevk, rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 26 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 154907 | ||
Steve Orvell
When setting `innerHTML` or using `insertAdjacentHTML` on an element or shadowRoot with a customElementRegistry set to null, any custom element candidates in the parsed HTML should not customize based on step 7 of "parsing HTML fragments" (https://html.spec.whatwg.org/#parsing-html-fragments).
However, they can customize in some cases which results in a customized custom element with a null customElementRegistry.
See reproduction: https://codepen.io/Steve-Orvell/pen/RNrroxV?editors=1000
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/161893045>
Radar WebKit Bug Importer
<rdar://problem/161893031>
Ahmad Saleem
Syncing tests here - https://github.com/WebKit/WebKit/pull/53067 added by Blink - https://chromium-review.googlesource.com/c/chromium/src/+/7023674