Re: [w3c/webcomponents] [idea] Allowing custom element registrations on per-shadow-root basis. (#488)

There are bigger problems, e.g. how CSS selectors or the HTML parser could work given how they both assume a single global namespace. Consider a selector `some-element { color: blue; }` for example, or a DocumentFragment containing `some-element` which is parsed once but whose elements could be inserted anywhere. If there are multiple definitions for some-element floating around all this falls apart.

React sidesteps these issues by moving away from HTML semantics in favor of just divs everywhere, and tracking the metadata seperately. Custom elements is the opposite of that, actually using and working with the DOM instead of avoiding it and treating it as a rendering layer. So I don't think there's really any interest in proposals to move away from that.

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