-
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
Can't edit TextInput when Talkback is enabled and there is a Touchable before the input #17042
Comments
Same thing happens on 0.49.3 |
Still can't find any workaround for this problem. Seems to me that it only occurs on Android SDK 23. Do you guys have any solution for this? |
Sometimes the input works, but most of the time it doesn't. |
The same problem occurs to me. Still no solution. Version: 0.49.3. |
Anyone has a solution for this? |
Still struggling with this. Has anyone found a solution? |
Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version? I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer. |
If I open a new issue against 0.53.0 it will just be closed when 0.54.0 is out. 😂 Whoever needs this fix can just fork RN and merge my PR. |
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Windows 10
Node: 8.2.1
Yarn: 0.27.5
npm: 5.3.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version 2.3.0.0 AI-162.4069837
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.4 => 0.50.4
Target Platform: Android (API 23)
Steps to Reproduce
Expected Behavior
Keyboard opens and you can start edit the input.
Actual Behavior
Focus changes to button and the button is pressed!
Reproducible Demo
https://github.com/victor-carvalho/rn-accessibility-bug-demo
Folow the steps explained before.
The text was updated successfully, but these errors were encountered: