# custom-elements-no-builtin **Repository Path**: mirrors_WebReflection/custom-elements-no-builtin ## Basic Information - **Project Name**: custom-elements-no-builtin - **Description**: A customElements polyfill, without builtin extends, targeting IE11+ and other browsers. - **Primary Language**: Unknown - **License**: Not specified - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2020-08-19 - **Last Updated**: 2025-12-27 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Custom Elements w/out Builtin for IE11+ and legacy. **Social Media Photo by [Joanna Kosinska](https://unsplash.com/@joannakosinska) on [Unsplash](https://unsplash.com/)** A customElements polyfill, without builtin extends, targeting IE11+ and other legacy browsers. * to add builtin extends, add [custom-elements-builtin](https://github.com/WebReflection/custom-elements-builtin#readme) on demand * for full V1 API compliance, ditch this module and use [custom-elements](https://github.com/WebReflection/custom-elements#readme) instead * for even more legacy browsers, ditch this module and use [document-register-element](https://github.com/WebReflection/document-register-element#readme) instead ## How To Test Please use features detection to avoid including this polyfill in every browser, considering that this replaces native `customElements`, if present, so that it would add unnecessary code to parse and execute in every browser that supports Custom Elements builtin natively already. ```html ``` **P.S.** the `\x2f` is not a typo, it's exactly how you should write it or your page layout will break! - - - ## To Keep In Mind This is *not* a _ShadowDOM_ polyfill, this is just the current [Custom Elements V1 as specified by standard bodies](https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-api) *without* builtin extends.