feat: add keyboardPrediction prop #7664
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tangjinzhou Please help me take a look at this. |
…users search, similar to earlier versions.
thinhbuzz
force-pushed
the
feature/keyboard-prediction
branch
from
6e4db8e
to
2e76570
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
add keyboardPrediction prop to restored previous behavior when users search, similar to earlier versions.
This PR will add the option to support features related to composition events without breaking the old behavior.
The new change in version 4.2.* prevented the current behavior of inputs from being completely broken, causing nearly all of our apps to break upon upgrade.
2024-06-17.14-12-06.mp4