Add support for the input type=range

[andybak]

Originally filed here: #1189

(This was incorrectly closed and despite requests to reopen, has remained closed so I'm reposting as a new ticket. For future reference, closing old tickets due to lack of activity is probably not a good idea.)

With multiple inputs to the same model doesn't play ball. It works as an input but updating it to a value set from another input always fails. Even if the source is also constrained as numeric (type="range" in chrome). This is due to the model being stored as a string.

Demo: http://jsfiddle.net/TXazw/5/Edit
Edit any input except the number and everything updates except the number input. Edit the number input and everything works fine.

A workaround is included. Uncomment parseFloat line and all inputs work correctly.

Should values not be automatically parsed when applied to a number type input? At the very least type="range" should be outputting a number rather than a string.

Discussed in the group:
https://groups.google.com/forum/?fromgroups#!topic/angular/Ecjx2fo8Qvk

[mlegenhausen]

+1

[ludoblues]

+1

[adamnbowen]

+1

[kazekagegaara]

+1

[ashclarke]

+1

[marcelbuesing]

+1

[vchirkov]

+1

[lgarron]

Indeed. It sounds petty, and it's probably easy to learn how to write a directive to fix this by passing through parseFloat(), but it's kind of annoying that a binding for input[type=range] is a string instead of a number.
Even if Javascript sometimes uses strings where something else would be suited better, this breaks the principle of least surprise, and has already caused me to create bugs.

Most use cases of input ranges will expect/need a number, and it's not terribly inefficient to support that.

[mismith]

+1

[c9s]

+1..

It should have something like ns-type="integer" or ns-type="float"

[lcerveau]

+1

[mlison]

+1