Can't share a data-ng-model between <input type="number" /> and <input type="range" />

[zippy1981]

I demonstrate the issue in a plunkr here . This stackoverflow answer describes the issue in detail.

Simply put, at least in chrome <input type="number" />.value is a number. and <input type="range" />.value is a string, so that's what is breaking the data-ng-model binding. That could be fixed with some casting with the ngModel directive (and possibly the ngBind directive).

On another note, the w3c spec for number input and range input both say the value should be a string representation of a number. Is this worth filing a bug with chrome over?

[Narretz]

Hey @zippy1981, I edited your post so that the html tags show up. The general problem is that currently angular has no special range handling, but if it is added, this should be considered.

[Narretz]

We are working on this (finally). Closing as a duplicate of #5892