Create ADR: Scoped components/ scoped elements #99
Description
The browser as only one space (custom registry) to store tagnames. This could to lead to collision in the tagnames (the componts could have the same tagnames). This means that plug-ins cannot be independent (or risk of breakages). The problem arrises when their are multiple versions for the same tagname.
Current workaround: assumption that the API stays the same. This does not have to be true in the distributed architecture we are after
Shorttime solution:
Everybody uses the same MWC version (latest version)
Pro: works
Con: everybody should stick to the same version
We cannot backport the plug-ins to the current/old OpenSCD due to version conficts
Another solution:
Scope tagnames
Pro:
Con: a lot of work to migrate and
Long-term solution:
https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md
https://chromestatus.com/feature/5090435261792256
Background information:
https://open-wc.org/docs/development/scoped-elements/
material-components/material-web#2010
Open questions:
How to handle MWC 3?
The solution could be converted into an ADR.