The customElements
read-only property of the Window
interface returns a reference to the CustomElementRegistry
object, which can be used to register new custom elements and get information about previously registered custom elements.
Examples
The most common example you'll see of this property being used is to get access to the CustomElementRegistry.define()
method to define and register a new custom element, e.g.:
let customElementRegistry = window.customElements; customElementRegistry.define('my-custom-element', MyCustomElement);
However, it is usually shortened to something like the following:
customElements.define('element-details', class extends HTMLElement { constructor() { super(); const template = document .getElementById('element-details-template') .content; const shadowRoot = this.attachShadow({mode: 'open'}) .appendChild(template.cloneNode(true)); } } );
See our web-components-examples repo for more usage examples.
Specification
Specification | Status | Comment |
---|---|---|
HTML Living Standard The definition of 'window.customElements' in that specification. |
Living Standard | Initial definition. |
Browser compatibility
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
customElements | Chrome Full support 54 | Edge Full support 79 | Firefox
Full support
63
| IE No support No | Opera Full support 41 | Safari Full support 10.1 | WebView Android Full support 54 | Chrome Android Full support 54 | Firefox Android
Full support
63
| Opera Android Full support 41 | Safari iOS Full support 10.3 | Samsung Internet Android Full support 6.0 |
Legend
- Full support
- Full support
- No support
- No support
- User must explicitly enable this feature.
- User must explicitly enable this feature.