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

> If you don't see the power that comes with Vue/React/Angular/etc on component-scoped naming of components ...

it's not that I don't see the power, I haven't even read this thread because is from 2016 and after a quick scan I've noticed more than a person involved with the process and the implementation said already it's not gonna happen.

I also don't buy the issue because if this is the reason:

> We use web components to load functionality from different services/locations with different development lifecycles

sounds to me like looking for troubles. What do you mean you don't know what you are loading?
 
Has the term XCS came up already? That's _Cross Component Scripting_ which is IMO as bad as XSS.

We managed to make npm modules name convention good enough for the biggest open source repository out there, I am sure we can survive with current Custom Elements global naming status for the time being.

I rather would like to see Custom Elements V1 out in every browser and as of today I have zero interest in making Custom Elements any different from the current status, the only bit I honestly miss is the abiity to tell when a node has been upgraded.

The name? I don't care, use prefixes like we do in npm and every other global shared place.

-- 
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-341776476