-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Scope non-scoped (global) registries to a single document #11472
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
Let the global custom element registry not escape its document for now. We throw an exception to give us some wiggle room in the future. DOM issue and PR: whatwg/dom#1390 & whatwg/dom#1392. Tests: TODO.
@ja-y-son to review for Chromium |
Do we want to apply similar constraint while attaching shadow using |
Yes we do. See the corresponding DOM PR. |
The changes lgtm! |
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.
LGTM
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.
Editoral LGTM. For implementer support I defer to @mfreed7.
Align with the changes in whatwg/dom#1392 and whatwg/html#11472, add many more tests, and correct several tests.
This preserves existing behavior. We throw exceptions in certain corner cases to give us some wiggle room in the future. Corresponding HTML PR: whatwg/html#11472. Tests: web-platform-tests/wpt#53791. Fixes #1390.
Post-merge, but this LGTM. |
Let the global custom element registry not escape its document for now. We throw an exception to give us some wiggle room in the future.
DOM issue and PR: whatwg/dom#1390 & whatwg/dom#1392.
Tests: web-platform-tests/wpt#53791.
(See WHATWG Working Mode: Changes for more details.)
/custom-elements.html ( diff )