[Android] TextInput where multiline is true doesn't allow to set returnKeyType
See original GitHub issueDescription
returnKeyType
does not work on Android with multi line props set to true
returnLabelType
seems to be the same. The problem is on iOS it works well, this is not persistent and be able to display a Text on multiple line without linebreak become too much hard.
Reproduction
<TextInput multiline={true} returnKeyType={"done"}/>
works on iOS but not on Android.
Solution
I found some native solution on stackoverflow but nothing in JS:
Maybe I am wrong and there is a solution to display a textinput on multiple line without carriage returns and action Done but I didn’t find a solution…
Additional Information
- React Native version: *
- Platform: Android
- Operating System: *
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Dismiss keyboard in multiline TextInput in React native
TextInput has a blurOnSubmit prop; when set to true, the return key dismisses the keyboard. However currently the prop does not work on ......
Read more >TextInput - React Native
Use it with multiline set to true to be able to fill the lines. Type. number. onBlur . Callback that is called when...
Read more >aria-multiline - Accessibility - MDN Web Docs - Mozilla
The aria-multiline attribute indicates whether a textbox accepts multiple lines of input or only a single line.
Read more >IPhoneProps | amplify-js
Determines the types of data converted to clickable URLs in the text input. Only valid if multiline={true} and editable={false} .
Read more >React Native Text Input Component - GeeksforGeeks
By default, autoCompleteType is true in all android devices. ... multiline: This allows to have multiple lines in text input.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This pr should fix this issue: https://github.com/facebook/react-native/pull/11125
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.