Inverted FlatList scroll issue on Android
See original GitHub issueHi.
I’ve found a bug. If you pass inverted
prop to FlatList
with RNGH scroll, then FlatList
would scroll in opposite direction sometimes if you make short quick scroll gestures. This happens on Android only. iOS isn’t affected.
See the video. Notice directions of gestures I make.
Check testcase repo. It’s easily reproducible.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Long text in inverted Flatlist causes huge performance drop on ...
As @nero2009 mention it has issue with Android devices for lag scrolling (not smooth like in iOS). If you are using react-native-gifted-chat and ......
Read more >Prevent inverted Flatlist from scrolling to bottom when new ...
The problem is that if add items to the bottom, it instantly scrolls to the bottom of the list. That means that the...
Read more >Anyone built a Chat app with React Native lately? - Reddit
Tried inverting the FlatList which made it drop to ~20 fps on my Android device, and inverting with styling caused weird empty spaces...
Read more >FlatList - React Native
Scrolls to the item at the specified index such that it is positioned in the viewable area such that viewPosition 0 places it...
Read more >Developers - Inverted FlatList scroll issue on Android - - Bountysource
Hi. I've found a bug. If you pass inverted prop to FlatList with RNGH scroll, then FlatList would scroll in opposite direction sometimes...
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
Looks like it was fixed in RN (and Expo) source code in November: https://github.com/facebook/react-native/commit/b971c5beb8c7f90543ea037194790142f4f57c80
I’ve tested my testcase with the latest RNGH and
react-native@0.58.0-rc.3
and it seems that the issue is indeed fixed. Therefore closing this issue as resolved.