Time to compare again? (webcompents/custom-elements)

[wbern]

Time to compare again? (webcompents/custom-elements)

[WebReflection]

So, this project has been about Custom Elements only since about ever, and its successor is @ungap/custom-elements-builtin.

Web Components, as defined by standards, have (used to be 4 but ...) 3 sub proposals: Shadow DOM, Custom Elements, and the AFAIK dead HTML Imports idea.

The Template element somehow got out of that Wikipedia page.

Accordingly, you'll never find Shadow DOM in here for at least two reasons:

• Custom Elements, and builtin extends, don't need ShadowDOM, it's a specification a part
• ShadowDOM cannot be polyfilled, so that the closest attempt I've made is attachShadow, which provides an extremely minimal attempt at simulating ShadowDOM.

In few words, ShadowDOM is a specification a part, it cannot be reliably polyfilled, because old browsers don't have its capabilities, and every polyfill for ShadowDOM is inherently broken, but evangelists/advocates wont tell this story to anyone.

TL;DR no, ShadowDOM has no place in here, because it's a polyfill/specification a part, and it's a broken promise itself, as polyfill.

Apologies for not answering the way you hoped for, but that's just the reality.

[WebReflection]

by the way, if you're looking for a helper that doesn't need ShadowDOM and yet let you configure in a better way CSS for any Custom Element, check µce out, as it covers it all, without ShadowDOM in between (and yet, it's compatible with ShadowDOM, so you have a future proof helper right there)