KeyboardAvoidingView with ScrollView inside -> no animation on keyboard show/hide
See original GitHub issueDescription
Consider this structure:
<KeyboardAvoidingView ...>
<FlatList ...> // or any other element that has `ScrollView` (ie `ListView`/`ScrollView` itself)
<TextInput ...>
</KeyboardAvoidingView>
When TextInput
is focused and keyboard animation happens TextInput
animates as expected, but ScrollView
changes its height without any animation.
Reproduction
https://sketch.expo.io/B1JIYaynx
Additional Information
- React Native version: 0.43
- Platform: iOS
Issue Analytics
- State:
- Created 6 years ago
- Reactions:19
- Comments:10 (3 by maintainers)
Top Results From Across the Web
KeyboardAvoidingView with ScrollView - Stack Overflow
I have many TextInputs in one component (sum of TextInputs height is bigger then device height), and once the keyboard appears, I have...
Read more >keyboard avoiding view not working with scrollview - You.com
I just have to use fixed height for my main container and inside that I can use flex layout. And If keyboard is...
Read more >KeyboardAvoidingView has got to be one of the most ... - Reddit
I can't implement a ScrollView inside of it without it cutting off the ... Listen to the keyboard show/hide events, and adjust the...
Read more >Using KeyboardAwareScrollView and KeyboardAvoidingView ...
This tutorial explains what KeyboardAvoidingView and KeyboardAwareScrollView are and how to use them for different purposes.
Read more >How to control what keyboard pushes up-React Native
</ScrollView>. Shri ram 41. score:13. 'use strict' import { ... , KeyboardAvoidingView } from 'react-native' class Test extends Component { constructor ...
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
We’re cutting down on the number of outstanding issues, in order to allow us to focus. I’m closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why. PRs are always welcome.
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.