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

I think you’re on the right track that it would need to behave something like that @mbostock. I.E. what’s being disassociated in the registry is ‘this tag name points at this definition’, like setting the _name_ and _local name_ parts of the definition to null. I think that would imply in turn that `new OriginalConstructor` would need to throw.

I think this would create the possible scenario of multiple elements with the same tag name occurring with two or more non-unknown meanings in the DOM. I don’t think that can currently happen with autonomous elements and am unsure what implications it might have.

-- 
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-557832587

Received on Saturday, 23 November 2019 21:03:04 UTC