Re: [WICG/webcomponents] Cleaning up (undefining) custom elements? (#754)

> > It wasn't really an oversight. We specifically designed so that custom element can't be redefined since allowing re-definition raises all sorts of design questions we weren't comfortable answering at the time. If you're interested in this issue getting any traction, as I have stated numerous times earlier in the thread, please follow up with the discussion of scoped custom element registry.
> 
> By no means I'm saying the current spec is done haphazardly, I'm sure a lot more deliberation than myself thinking have gone into it. Regarding scoped registry, I've already answered why I think that doesn't resolve the problem completely, in the case of re-loading the same contents.

Sigh... this is the third time I'm having to explain this. Adding the capability to re-define custom elements or delete the definition, we need to [answer some questions I had previously stated](https://github.com/WICG/webcomponents/issues/754#issuecomment-557774809). As I have [previously stated](https://github.com/WICG/webcomponents/issues/754#issuecomment-781749398), figuring out how scoped custom element registry would answer most of those questions. So, if we have figured out how to implement scoped custom element registry in the browsers, it would pave a way to add the ability to clean up custom element definitions in the global scope as well. So the step 1 of this feature is to work on the scoped custom element registry.

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

Message ID: <WICG/webcomponents/issues/754/1090331400@github.com>