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

In addition to defining & collecting compelling use cases, here are some of additional issues / edge cases that need to be sorted out off the top of my head:
 * What happens to exiting elements' prototype & its methods.
 * What happens when someone clones an existing element, which is now "undefined".
 * What happens when when a custom element reaction callback or upgrading a custom element (inadvertently) undefines itself before draining some of items in [custom element reaction queue](https://html.spec.whatwg.org/multipage/custom-elements.html#custom-element-reaction-queue).

I'm sure there is a lot more cases to consider that I haven't even thought about.

-- 
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/754#issuecomment-557774809