- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 05 Apr 2022 17:00:41 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 6 April 2022 00:00:53 UTC
> > @imdavidmin @getflourish if you're looking for hot module reload, testing, etc, you can still do all that in user-land, here is a POC of that for you to test: > > https://github.com/caridy/redefine-custom-elements > > Respectfully, it is not difficult to work something out in Javascript or with a library. The issue at hand here is what I believe to be a design oversight in Web standard specs. I already am working around the issue but just not very elegant. 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. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/754#issuecomment-1089546707 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/754/1089546707@github.com>
Received on Wednesday, 6 April 2022 00:00:53 UTC