3 ms·

What I've heard is that Chrome shipped an unfinished early version of the web components spec, and now there are sites relying on it because it works in Chrome

by sfink 7y ago

What I've heard is that Chrome shipped an unfinished early version of the web components spec, and now there are sites relying on it because it works in Chrome and that's good enough. I think the spec has been more or less finalized now? I'm not sure whether it's shipping in both browsers, though. Something is (eg for firefox it's since 63), but I don't know exactly what. I believe YouTube uses a whole framework based on the preratified spec?

dragonsh 7y ago
Even though the spec is finalized there are enough variation on support on different browsers leading to substantial efforts to make a web components based pwa work on multu-browser. If it had been worked out properly there's isn't any need of react or angular except for a state management library, since the views and components is taken care of by the browser directly.