Re: [WICG/webcomponents] [scoped-registries] Interaction with HTML element's overridden constructor steps (Issue #969) from Nicolas Gilbert on 2023-02-26 (public-webapps-github@w3.org from February 2023)

From: Nicolas Gilbert <notifications@github.com>
Date: Sun, 26 Feb 2023 11:00:59 -0800
To: WICG/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <WICG/webcomponents/issues/969/1445437108@github.com>

I agree with you, preventing the same constructor from being defined on multiple registry is clearer. This seems a reasonable limitation, I personally prefer that to stoping constructor re-entry, as edge case at is is. There already seem to be an association between the constructor and its registry as only a defined custom element can be instantiated through its constructor, this seems like a logical extension. I could see the use for some helper though:  `CustomElementRegistry.getRegistryOf`, `CustomElementRegistry#isRegistryOf`, etc.

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

Message ID: <WICG/webcomponents/issues/969/1445437108@github.com>

Received on Sunday, 26 February 2023 19:01:12 UTC