Re: [webcomponents] Permit retrieval of registered classes from window.customElements (#445)

@domenic I see you noticed that ```Element.prototype.attributes``` is a complex thing. Let me write some ideas.
> A CustomElementsRegistry's list of defined local names is the list containing all of the local names of the custom element definitions in the registry.

1. As mentioned at "2.4 The CustomElementsRegistry interface" the ```window.customElements``` is a list.
2. As mentioned at "3.1 HTML+: The Window object" I see that ```window.customElements``` is an instance of  "2.4 The CustomElementsRegistry interface".

Then,
1. Is it necessary to expose the list from the registry?
2. If expose it, should be used the root element ```window.customElements```?

I think that to expose the list of defined custom elements should be used an extra attribute... something like

```javascript 
window.customElements.definitions
// or
window.customElements.elements
// or something similar
```


But...
The same name ``` window.customElements``` states that we're working with custom elements.
So. We've an object ```window.customElements``` that
1) defines new custom elements
2) behaves like a list

---
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/445#issuecomment-199357789