Fix/onchange text input

[Gpx]

Rebase of #141

It looks like React handles the change event differently from what a browser does.

In a browser:

keydown
keypress
input
keyup
change

And change fires only after the input loses focus.

In React this is the sequence:

keydown
keypress
input
change
keyup

change fires without need to blur the input.

You can try both sequences here and here.

@calebeby what do you think? Does it make sense to you?

[calebeby]

@Gpx In react for text inputs, onChange and onInput are exactly the same. For text inputs, React's onChange actually listens to the input event. So if user-event fires a DOM change event the same way a real user does, it won't affect React

In Preact and Vue, onChange/@change listen for the actual DOM change event, and if people want to listen for the input event then they use onInput/@input

[codecov-io]

Codecov Report

Merging #147 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
+ Coverage   96.52%   96.58%   +0.05%     
==========================================
  Files           1        1              
  Lines         115      117       +2     
  Branches       27       27              
==========================================
+ Hits          111      113       +2     
  Misses          4        4

Impacted Files	Coverage Δ
src/index.js	96.58% <100%> (+0.05%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ceff569...8ea17a1. Read the comment docs.

[Gpx]

🎉 This PR is included in version 4.2.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀