-
Notifications
You must be signed in to change notification settings - Fork 320
Make attachShadow() use the global registry by default #1409
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
Conversation
This significantly improves the reuse of custom elements in different registries. Tests: web-platform-tests/wpt#55248. Fixes #1407.
keithamus
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes +1; consider Mozilla interested.
Sounds reasonable to me. But I'd love if @dandclark could also take a look.
Quick thing: is there already an MDN issue filed for SCER overall? The existing page for |
|
The original DOM PR (and HTML PR) has all the relevant pointers: #1341. |
Ahh great - thanks. MDN issue here: mdn/content#38266 |
whatwg/dom#1409 changed where attachShadow() obtains its registry so the serialization should account for that as well. Tests: web-platform-tests/wpt#56134. Fixes #11892.
…trees In whatwg/dom#1409 this was changed for attachShadow(), but we forgot to change the HTML parser at the same time. Tests: web-platform-tests/wpt#56134. Fixes #11947.
…trees In whatwg/dom#1409 this was changed for attachShadow(), but we forgot to change the HTML parser at the same time. Tests: web-platform-tests/wpt#56134. Fixes #11947.
whatwg/dom#1409 changed where attachShadow() obtains its registry so the serialization should account for that as well. Tests: web-platform-tests/wpt#56134. Fixes #11892.
This significantly improves the reuse of custom elements in different registries.
Tests: web-platform-tests/wpt#55248.
Fixes #1407.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff