input type=range onChange should fire when changing the value using the keyboard arrow keys

[subtleGradient]

[sophiebits]

Chrome doesn't fire the input event when a range is modified using arrow keys, but Firefox does.

[jessep]

Chrome fires a 'change' event when you change it with keyboard. Possible to use 'change' instead of input?

[sophiebits]

In Chrome beta and Firefox, 'change' doesn't fire when dragging until mouseup so we should listen to input here too.

[eddhannay]

I made a JSFiddle to test this: http://jsfiddle.net/vqnMU/embedded/result/

React seems to be listening for input, and triggering input & change whenever it occurs.

Focusing the slider and pressing right:

Browser	Event	React Event
Chrome 34.0.1847.131**	Change	-
Safari 7.0.3	Change	-
Chrome Canary	Input, Change	Input, Change
Firefox 29*	Input	Input, Change
IE 10	Change	-

* Firefox triggers change on blur

Additionally for dragging:

Browser	Event	React Event
Chrome 34.0.1847.131	Input*	Input, Change
Safari 7.0.3	Input, Change	Input, Change
Chrome Canary	Input*	Input, Change
Firefox 29	Input*	Input, Change
IE 10	Change	-

* These browsers all trigger change on drag end

Editing ChangeEventPlugin to listen for change events on all input types (35e7aa4) appears to fix React's change & input event handling for all of the above browsers. Should I make a pull request, or is there a reason that the plugin was only listening for change events on file inputs that I'm missing?

[locks]

I just ran into this problem when trying to port a widget I have to React.
Can someone in the core give some feedback on whether @eddhannay's suggestion would/wouldn't work? Thanks :)

[syranide]

@locks I would recommend implementing your own, it seems like all the HTML input elements come with a bunch of inconsistencies that can be hard to normalize and are basically unstyle:able.

[sophiebits]

@syranide I think we should attempt to support all the built-in inputs at least mostly-reasonably.

[syranide]

@spicyj Certainly! But there are lots of weird things that we can't fix... like not being able to read the value of type="number" if it isn't strictly numeric, etc.

[dmmalam]

+1

Any workaround for IE10+ to get react to fire a synth onChange, on a browser onchange for range inputs

[chooven]

+1 for input on IE10+ firing onChange

[kwhitaker]

+1 to all the +1