It’s because they display—and behave—wildly differently in different browsers. This has been the story of tons of HTML5 “widgets”. I know this isn’t quite a wi

It’s because they display—and behave—wildly differently in different browsers. This has been the story of tons of HTML5 “widgets”. I know this isn’t quite a widget, but when something as simple as input type=“number” was introduced, I was excited because it could be used to call up the mobile keyboard for numeric input. (Say for a zip code, which is a common use case). But unfortunately, it can also be changed via your mouse’s scroll wheel, accidentally, so I’m stuck using input type=“tel” for everything. (Do you want to scroll to your zip code?) The problem with these things is you can’t just push out improvements and fixes. Everything has to be backwards-compatible and I feel like they’re never nearly good enough at the beginning.