-
Notifications
You must be signed in to change notification settings - Fork 252
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
Fix unexpected behavior with setSelectionRange on inputs in the browser #679
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9efb5b1:
|
Codecov Report
@@ Coverage Diff @@
## master #679 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 50 50
Lines 932 934 +2
Branches 363 364 +1
=========================================
+ Hits 932 934 +2
Continue to review full report at Codecov.
|
@all-contributors add @sydneyjodon-wk code |
I've put up a pull request to add @sydneyjodon-wk! 🎉 |
🎉 This PR is included in version 13.1.9 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
What:
userEvent.type
with selection range does not work as expected in the browser. Closes #677Why:
When an input or textarea is clicked, the parent div is selected and the
Selection
range should not be updated at the end ofsetSelectionRange
.How:
Skip setting
Selection
range for<input>
and<textarea>
insetSelectionRange
utility. (see comment on issue)Checklist: