Re: [WICG/webcomponents] Updating Element Registration. (#820)

>Are there any discussions to support updating the implementation of a custom element definition? (Searched and did not spot anything obvious)

@pshihn See #754. It would be great if it were left opened.

> Have you tried implementing this in user space via a proxy class of sorts?

@annevk That requires the CE author to write a framework rather than just using plain CEs. It would take the fun out of writing CEs.

> Given most of native apps don't have the ability to monkey patch itself while running, I have a hard time believing that many web apps would opt to do this.

Of all systems that exist, the web may be the one that is best at exactly this.

I think it may be great to allow devs to undefine elements, so they can then redefine them with new classes. This is also related to the ability to dynamically change the registry that is associated with a ShadowRoot (related: https://github.com/WICG/webcomponents/issues/914 and https://github.com/WICG/webcomponents/issues/907).

The ability to update applications without a full-refresh is a super compelling use case. If web could do it, and native can't, in my opinion that gives web a far superior advantage. Just because native can't doesn't mean web shouldn't.

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