Re: [w3c/webcomponents] [templates] Is a global registry of template processors the right idea? (#681)

Why was the global registry of Custom Elements unavoidable? The fact it exists is one of the reasons I still avoid custom elements for the most part. I can't see why it wouldn't be possible to have `shadowRoot.customElements` in addition to `window.customElements`.

Regardless I think template types shouldn't make the same mistake as otherwise there's going to be an even *higher* chance of namespace collisions for distributed templates given names like `for-each`/`if`/etc will almost certainly be commonplace.

-- 
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/681#issuecomment-341886424