Re: [webcomponents] Support renaming, aliasing, or namespacing imported elements (#344)

It doesn't really solve the issue if they both must have the same name. Rather, it makes it easier for app authors to choose the names, thus avoiding any name collisions in the first place.

The sacrifice is that library authors cannot use innerHTML (since they don't know what tag name the app author will use) and cannot target subcomponents with CSS by tag name (for the same reason).

> Is there also the possibility of simply using unique registries? Or more simply I guess on a unique document, rather than the global document.

@esprehn had some cool ideas along these lines, which partially helped solve the CSS problem (but still left innerHTML broken, as it always is in multi-document scenarios). I think it's promising.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/344#issuecomment-166760439