-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to v11.1.0 causes type method to fill Input incorrectly #309
Comments
I think I know what's going on here, I'll probably be able to fix it this morning, but if you'd like to beat me to it you're more than welcome! Even providing me with a failing test case as a PR would be helpful and welcome 😁 |
i can confirm that 11.2 still acts differently than old version, seems to be working like you had replace mode enabled in typing and occasionally loosing some letters? very strange |
10.4.1 seems to be last version that was working more like i would expect typing to work, so appending text correctly at the end |
I figured it out. Pushing a fix in a moment. |
@all-contributors please add @kelvinlzhang for bugs |
I've put up a pull request to add @kelvinlzhang! 🎉 |
@all-contributors please add @krzysztof-hellostudio for bugs |
I've put up a pull request to add @krzysztof-hellostudio! 🎉 |
🎉 This issue has been resolved in version 11.2.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Really appreciate the quick turnaround on this 😄 |
What tpict said, thanks @kentcdodds! 🚀 |
@testing-library/user-event
version: 11.1.0STR:
user.type
instead offireEvent
to fill the input--env=jest-environment-jsdom-sixteen
and observe that it failsWhat happened:
Reproduction repository: https://github.com/kelvinlzhang/user-event-test
Problem description:
type
fails to fill the input correctly. If you downgrade to 11.0.0 the test will pass. On another repo this exact upgrade causes anInvalidStateError
and I had to reinstall jest-environment-jsdom-sixteen. This comment, #307 (comment), also explains another issue I have been unable to reproduce on a fresh app but occurred with the same dependencies.The text was updated successfully, but these errors were encountered: