Re: [WICG/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

@dannymcgee we use [this polyfill](https://github.com/ungap/custom-elements) in production and zero issues whatsoever. It leaves untouched all browsers that support builtin extends, it patches `whenDefined` only to browsers not supporting latest standard, it brings customElements to IE11 and old Edge, and it patches Safari builtin extends capabilities. Its size is irrelevant compared to any framework/library, and whatever decision/change/proposal will be on the plate, you'll need a polyfill regardless for such proposal because no browser would implement it until it ships everywhere (5 years or more?) so I don't see why not using a polyfill now as well. Also worth saying there's a "*patch Safari only*" module, behind the scene, but feature detecting it is awkward and error prone, while the module I've just mentioned does that for you.
I hope this helps.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/509#issuecomment-732741975