Re: [WICG/webcomponents] [scoped-registries] reduce pain by preventing logic from ever touching non-upgraded custom elements (Issue #960) from Ryosuke Niwa on 2022-07-20 (public-webapps-github@w3.org from July 2022)

From: Ryosuke Niwa <notifications@github.com>
Date: Tue, 19 Jul 2022 20:47:58 -0700
To: WICG/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <WICG/webcomponents/issues/960/1189787741@github.com>

So that would mean we'd have a mixture of elements that get upgraded & not upgraded in a single tree. That sounds very confusing for users of those components to me. For the behavior to make sense, it really needs to be done per registry, not element by element. Otherwise, each custom element will have to worry about not just which custom element is defined but also how they're defined before using them. That seems to make things more complicated, not less.

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

Message ID: <WICG/webcomponents/issues/960/1189787741@github.com>

Received on Wednesday, 20 July 2022 03:48:20 UTC