Should we let the keyboard emit 'change' event with every input?

[lcb931023]

The word 'change' makes sense to be used for our effects on <input>, <select>, or <textarea>. However the behavior is inconsistent depending on which input method we use, and on which platform.

https://developer.mozilla.org/en-US/docs/Web/Events/change

Different browsers do not always agree whether a change event should be fired for certain types of interaction. For example, keyboard navigation in elements never fires a change event in Gecko until the user hits Enter or switches the focus away from the

[adammcfadden]

A bit late to the party here, but this update was made in this commit.

Adding the input and change events was specifically so that v-model would be able to work and pick up changes as they come in.