-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
onSelectionChange and onChangeText queues differently in android and ios #28752
Comments
@JoshuaGross or anyone from the space can help me! |
Expo SDK 37 relies on react native .61 Can you try this in a bare react native project using the latest version and see if you can reproduce the issue? |
|
@cruzach I updated my code expo to bare workflow But still, the issue happened in android |
|
|
Sounds like you have a standalone repro but I'm not seeing a link? |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
related to #28865 |
Description
When the input changes, the onChangeText triggers first in Android and onSelectionChanges triggers next. But in iPhone its vice verse.
React Native version:
react-native-cli: 2.0.1
react-native: n/a - not inside a React Native project directory (expo - sdk 57)
Steps To Reproduce
Add onSelectionChange and onCHangeText for a TextInput,
Change and see the log
Expected Results
Its should be consistent for both anyone in either way
I need the selection start and end to string manipulate for tag mentions. Due to this bug, we couldn't make the string logics based on the text input and caret selection.
Note: All the versions are latest up to yesterday.
The text was updated successfully, but these errors were encountered: