repro is here: https://glib-snowman.glitch.me/

1. click the down arrow of the <input type=number> a few times without moving the mouse
2. observe no change event is fired (after the first one)
3. wait a few more seconds. nothing
4. move the mouse a little
5. a change event is fired.

I can repro this current behavior back in Chrome 52, however Safari and Firefox reliably dispatch `change` events.

In my case I discovered this on https://knitlify.netlify.com/. IMO, the up/down controls on a number input encourage the user to use their mouse cursor, but not move the position--so I think this is quite common.

https://developer.mozilla.org/en-US/docs/Web/Events/change points out there are browser differences (and that `input` is a better event to use). I can understand why we'd throttle the `change` event, but *I feel like it should fire after a short timeout if there's no user activity*. 


Related issues:  issue 528985 ,  issue 691879 , probably others.