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

> in the downgrade case, disconnectedCallback runs, then prototypes are removed. Note that, reciprocally to upgrade, the downgraded instance may have remaining own props still present, which is totally fine. A future upgrade could re-use those again, for example, similar to how the very first upgrade may encounter existing own props and would need to deal with them.

Part of the trouble here is that JS itself has no generic concept of "object teardown" to build off of, so there can be no answer involving "transitioning" the original object that is not at best idiosyncractic and at worst incompatible with core language features like private fields (which will throw on attempted reallocation if definition is added back).

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

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