Expose a method to change keyboard instance internal state before input value change #2277
+149
−81
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hi I was developing a React app for a touchscreen device and I ran into the same touchscreen cursor problem linked here
Since it doesn't seem like they will be fixing this issue, I thought if we can't listen to the event fired, we could try to sync up the cursor location before we change the input value. All current methods are called after the fact, so I went ahead and created the method
beforeInputChange
with the keyboard instance passed to it.My use case will be calling
keyboard.setCaretPosition(inputRef.current.selectionStart, inputRef.current.selectionEnd)
. If possible I would rather not maintain a fork of this awesome library. Please let me know what you think, thanks!Checks
npm run coverage