Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)

At the virtual F2F in march the conclusion was to aim for a slimmed down version of https://github.com/w3c/webcomponents/pull/865:
- No inheritance between registries
- No `getDefinitions()`
- "newing" the constructor of a custom element will evaluate it in the scope of the global registry.

There was a concern raised by @rniwa about moving elements and it's associated custom element registry between iframes, because the custom element registries are backed by JS and native code. (if I recall correctly).

What's the process for moving forward with this? We need to update the proposal with what's agreed on, can I help with that? 

For the iframe part, does there need to be any investigation on the implementors side or do we just need to come up with a proposal on how to deal with this problem? 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/716#issuecomment-612822254