Fix typing into validated input types

[tpict]

What:

Temporarily sets the target element's type to text until the type function resolves

Why:

The type implementation depends on setSelectionRange which raises an error for validated input types like email, number

How:

Take a guess 😝

Checklist:

• Documentation N/A (?)
• Tests
• Typings N/A
• Ready to be merged

I did try replacing type with a getter property to log a warning along the lines of "hey, you're accessing type while typeing and the result will be inaccurate", but it turns out that it's referenced by testing machinery so frequently as to be useless. Does this behavior need to be documented anywhere?

[codecov]

Codecov Report

Merging #317 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #317      +/-   ##
==========================================
+ Coverage   99.31%   99.32%   +0.01%     
==========================================
  Files           2        3       +1     
  Lines         293      298       +5     
  Branches       74       76       +2     
==========================================
+ Hits          291      296       +5     
  Misses          2        2              

Impacted Files	Coverage Δ
src/index.js	98.88% <ø> (-0.01%)	⬇️
src/type.js	100.00% <100.00%> (ø)
src/utils.js	100.00% <100.00%> (ø)

---

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 5c11411...484183c. Read the comment docs.

[Meemaw]

Consider adding a case for multiple input types, like here https://github.com/testing-library/user-event/blob/master/src/__tests__/clear.js#L77

[kentcdodds]

I'm afraid this really isn't going to work. Changing the input's type will violate the principle of least surprise (especially with regard to async code and event handlers that may rely on the type being set to something specific).

In addition, it's not going to help people who try to set the selection range before typing.

I'm thinking the solution will be to assume that when the selectionStart is null, it's actually always at the end of the input. I think that's the best we can do.

Would you be able to add a test to make sure this works on an input with a number? await userEvent.type('12{backspace}34'). If it does not, could you make it work?

[kentcdodds]

Hey @tpict, so I was working on type fixing several bugs and I fixed this on my own. Thanks for your help anyway!