- From: Caridy Patiño <notifications@github.com>
- Date: Fri, 09 Feb 2024 09:30:22 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 9 February 2024 17:30:28 UTC
Few notes: 1. Curious what @rniwa and others implementers think about the `.run()` idea. I think that will be problematic to implement, but also I don't think we have no precedent in the standard libraries for such pattern, even though it is common in the user space. 2. I agree with @rwaldron assessment, it must work for existing registrations. If we create a new API that only scope elements if you control the creation of instances, well, that will be very limiting. 3. @nolanlawson for us at salesforce, I do think that we can work with the registration mechanism because we do control it (via virtualization or via framework when registering pivots). That means something like `customElements.define('x-foo', XFoo, {upgradeOnly: true})` from @sorvell might be good enough. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1043#issuecomment-1936315234 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1043/1936315234@github.com>
Received on Friday, 9 February 2024 17:30:28 UTC