Add range input to ChangeEventPlugin - Fixes #554

[eddhannay]

• Added type check for range inputs in to ChangeEventPlugin
• Added tests to check that native change events trigger synthetic events on range inputs but
  not text inputs

This replaces #1561, which enabled ChangeEventPlugin for all inputs.

[sophiebits]

For range inputs, we need to listen to both the input event and change event because as your research in #554 showed, not all browsers fire change. (We should not fire two events for a single change though even if we get both native events.)

[eddhannay]

Input events will still be tracked correctly, the difference is that React will no longer fire a synthetic input and synthetic change whenever a native input is triggered. All browsers will eventually trigger change, the difference is that IE10 will trigger it whenever the value changes, where the others will trigger it when the range loses focus.

I have made a JSFiddle here: http://jsfiddle.net/vqnMU/, and uploaded a copy of React with the patch here: https://edd.fm/test/react/react.min-fix.js, which you can switch to in the external resources panel. The result across browsers will be:

Browser event	React 0.10.0	This patch
Input	Input, Change	Input
Change	-	Change

There isn't a time at which we'll receive both native events simultaneously - at least I haven't seen a browser that fires both change and input for the exact same interaction, although they do both occur close together on most browsers when a value is select with the mouse. Is this somewhere that React's events should differ from the native events?

[sophiebits]

This patch isn't quite what we want – we'd instead like onChange to fire whenever the value changes (which probably means listening to both native events). If you want to take this on feel free to open a new PR – it'll probably take a bit of refactoring to ChangeEventPlugin.