Hacker News new | ask | show | jobs
by pjmlp 2581 days ago
Edge support is perfectly fine, and it is going to be replaced by Chrome anyway.

Firefox, Safari and Chrome based browsers are perfectly fine.

Opera is based on Bink nowadays.

ESR is not something that I regularly see in the wild.

In any case, I was speaking that only see this anti-WebComponents attitude in the React community.
1 comments
vetinari 2581 days ago
Safari doesn't support customized built-in elements, at all, and isn't going to. That is pretty far from being "perfectly fine".
link
pjmlp 2580 days ago
I see all green here.

https://www.webcomponents.org/

link
vetinari 2580 days ago
https://caniuse.com/#search=web%20components

The Shadow DOM and Custom Elements are not that kind of green it should be.

link
Touche 2580 days ago
That's silly, customized built-ins are not an essential feature. They are a nice to have. You can get by without ever using them, which is indeed what most people do. As does the subject of this discuss, the Lightning Web Components doesn't use that feature at all.
link
vetinari 2580 days ago
It also means, that you cannot use existing form controls for your custom element, you must build them up from scratch from divs, and relegate them into uncanny valley of not-quite-native, slightly-off elements.

Yes, it is possible to not use them; you can always make your life harder than necessary, you could also write an modern OS in assembly, for example, if you wanted to. If people are avoiding them today, one reason could be that they want their components to run in Safari.

link
csande17 2580 days ago
Even if you aren't able to inherit from a form element, can't you still `createElement` one and add it inside your custom element? Surely they don't force you to reimplement <input /> from scratch!
link