But that's true for all HTML5 features. I'm frankly glad that Mozilla has prioritized stuff like IndexedDB (not yet in Safari or Opera, Chrome using an outdated spec last I checked).
Unless there is a reason why input[type="range"] is more important than the stuff they are working on, I don't think we can really complain. Mozilla arguably has the fastest release cycle nowadays.
Luckily, new input types should be very easy to provide via polyfill. Personally, I'd rather Mozilla implement the features that can't be implemented by polyfill first.
Comments
Mainly because it's high profile.
But also because it can't be used until it's been in browsers for a long long time. So you need to get it in there early.
There is a HUGE lag time from when it's implemented to when it's usable.
But that's true for all HTML5 features. I'm frankly glad that Mozilla has prioritized stuff like IndexedDB (not yet in Safari or Opera, Chrome using an outdated spec last I checked).
Unless there is a reason why input[type="range"] is more important than the stuff they are working on, I don't think we can really complain. Mozilla arguably has the fastest release cycle nowadays.
Luckily, new input types should be very easy to provide via polyfill. Personally, I'd rather Mozilla implement the features that can't be implemented by polyfill first.
>But also because it can't be used until it's been in browsers for a long long time. So you need to get it in there early.
That was true once, but the autoupdating nature of Firefox and Chrome challenges that assertion.