fix: Issue with Korean Input: Loss of TextEditingRange When Alternating Consonant and Vowel #756
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
|
|
|
@kyungilcho On which platform did you test it? |
|
It was Android, Galaxy S7 tablet and Galaxy S20 smart phone. |
|
I have tried many different platforms(iOS tablet, iOS(17.x)) and I have faced same issue. Now I fixed the issue please test it and give me feed back if any issue occurs. |
|
The latest version 3.0.0 should include the fix for the text range composition issue. |
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.
#755
Previously, when Korean is editing, composing is not working correctly. composing region changed by the framework.