Re: [w3c/webcomponents] Lack of implementations of customized built-in elements is hurting Web Components (#648)

That is a fair comment regarding standardizing something that doesn't have consensus. OTOH, that is why polyfills exist, and if you look at caniuse.com I think it is clear there are many many things which will never be implemented by all browsers.

I guess my concern is that no vendor appears to be working on either a native implementation or a polyfill even, and even when the polyfill is available from the community, the flagship library promoting Custom Elements won't accept the PR.

Finally, the reasons that a vendor gives for not implementing a feature are often not clearly articulated to the community. In the case of customised built ins, we heard something about liskov substitution principle; with imports it was wait and see how modules turn out. Never any specifics, and certainly not done in public, like for example discourse.wicg.io/

-- 
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/648#issuecomment-324789470