Re: [whatwg/dom] Allow elements with a null customElementRegistry without declaratively and without Shadow DOM (Issue #1413)

sorvell left a comment (whatwg/dom#1413)

Trees without registries are helpful when DOM should be rendered and potentially manipulated independent of any specific knowledge of custom elements. Consider, for example, using a web framework to render or hydrate some DOM and a custom element based design system within that tree. The user could setup the framework (which may not work well with Shadow DOM) to use a null registry and load the design system independently. 

These types of scenarios are advanced, and they can come up when managing [micro frontend](https://en.wikipedia.org/wiki/Micro_frontend) architectures that have become somewhat popular in enterprise. In these cases there are often multiple independent "islands" rendered with multiple different frameworks and versions. They may use custom element based design systems to facilitate code re-use and interoperability between these islands, and scoped registries help ensure that the individual islands don't require sharing the same elements, code, and versions.

In these scenarios, it would be really useful to have a declarative, persistent tree with a null registry (without the need to use Shadow DOM).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1413#issuecomment-3393342472
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1413/3393342472@github.com>