Re: [WICG/webcomponents] [scoped-registries] Concerns about non-construction of scoped elements (Issue #987)

This is how I understand the situation:
1. A library defines two components `CompA` and `CompB`, where one has a callback that creates another as a light-dom child via constructor
2. Another developer creates another component, which uses `CompA` and `CompB` in its shadow tree. The shadow root also has a scoped registry with `CompA` and `CompB` registered.

Then the components break. The developer has no way to fix it on their side, but can either stop using scoped registries or  wait for the lib to migrate.

This means the current design of scoped registries is not fully backward-compatible.

@justinfagnani Your examples are still making constructor calls use a specific registry, and do not solve the case.

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

Message ID: <WICG/webcomponents/issues/987/1511613679@github.com>