2 ms·

The intent has always been that the most frequently used webcomponents will end up getting baked into the browser, and then into the HTML spec. That's nice in

The intent has always been that the most frequently used webcomponents will end up getting baked into the browser, and then into the HTML spec. That's nice in theory, but what's happening in reality is that no component is going to be standardized, and HTML remains stagnant for another 15 years.

nostrademons 11y ago
It's a little hard to make that argument when web components themselves aren't standardized yet, and are fully supported natively in only one of the major browsers. There's pretty ample evidence that common webdeveloper behavior does make it into the spec, eg. JQuery => querySelectorAll, Javascript animations => CSS transitions & animations, long-polling => websockets, common layouts => <header>/<footer>/<main>/<nav> elements, dropdowns => <details>/<summary> elements, the addition of date/datetime/color/number/range/tel input types, etc. If you're still coding HTML like you did in 2000, you are now very obsolete.