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

We discussed this in the last F2F, and after that @justinfagnani and I also discussed it offline.

When the issue does occur, it indeed leads to difficulties in migration, although still possible (see previous comments in this thread).

However, we think this doesn't lead to any major concern, because the issue relies on a pattern (component creating light-dom children) that is very rare (according to @justinfagnani's experience), and it's not a good pattern even without scoped registries as it breaks encapsulation. Also, the pattern (relying on a global constructor) seems fundamentally incompatible with any scoping efforts.

So we'll leave the current design of scoped registries as is.

The worst outcome is that such libraries will remain unmigrated, and they will still work as is without scoped registries. As this is a rare pattern, it shouldn't affect the adoption of scoped registries.

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

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