-
Notifications
You must be signed in to change notification settings - Fork 275
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
blank area always showing on each scroll #796
Comments
Refer to the docs. For example, you shouldn't include a |
But when I remove the key, the sort order changes during scroll. |
Yes we have same issue like I stated above, if we remove the key the images rearranged |
Have the same issue |
Facing the same issue. i am using @shopify/flash-list version 1.5.0 in my react native app. |
Have the same issue. "@shopify/flash-list": "^1.5.0", Is there any way out of this? Issue is closed but still facing it. |
Current behavior
i create an Explore page like Instagram, but with the same size for all images.
the issue is similar with this, but it is worse if the list contains an image.
if i change to flatlist, there is no more blank area but less performance
is it possible because of the Key props?
the problem is that when i remove the key props, the image order changes.
Expected behavior
"No more blank cells" as advertised
To Reproduce
just using this code
Platform:
Environment
System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (4) x64 Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
Memory: 5.70 GB / 15.55 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.13.2/bin/yarn
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
Watchman: 20220123.190932.0 - /usr/local/bin/watchman
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.18 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: ^0.70.7 => 0.70.7
npmGlobalPackages:
react-native: Not Found
The text was updated successfully, but these errors were encountered: