Re: [w3c/webcomponents] Scoped Custom Element Registries (#716)

@justinfagnani IMHO, A set of custom elements created as a _micro application_ may need its own closed event system because event names can conflict as you said.
And I think that system's scope is the same to its registry level.

> Most elements will not know the registry they are registered against, only the registry they define their dependencies in.

For example, if elements have `this.registry` field which allows the element to access its own registry, it may be worth more. Each element doesn't know other elements and they are created in independent js modules without including `xRegistry` reference as a closure, but they can fire closed events without name collision. 

-- 
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/716#issuecomment-384468383

Received on Wednesday, 25 April 2018 23:48:53 UTC