-
Notifications
You must be signed in to change notification settings - Fork 167
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
Sticky headers don't show correctly in Tabs.FlatList on iOS #136
Comments
This seems like a side effect of using
Unfortunately there's no other way on iOS to position the refresh control at the moment. There's a PR on it here: facebook/react-native#30737 If that PR is merged to React Native we'll have a way around this. One workaround would be to not use However, proper "below the header" refresh control positioning and sticky headers will not both work at the same time unless the upstream react-native PR is merged. |
Thank you for the clarification. That also explains why giving a ScrollView container top padding was only working on iOS and causing issues on Android ;). I don't use the refresh control but do like to have the iOS bounce effect below the header |
Hi! That React Native PR was merged. Are we able to use |
@damassi - feel free to play with the example app to see if it works now. If you need to make any modifications to the library, PRs are welcome. Please take a look at the CONTRIBUTING document as well. |
in v6.2.0 still exist this issue. Checked on |
yeah the issue persists, im on the latest everything |
Bump on this 🙏 |
any workarounds for this? |
First of all, great job on this component! v4 added some really nice and necessary features for us.
Current behavior
When you use the stickyHeaderIndices prop on a FlatList, the sticky elements don't scroll up when the header collapses. This happens only on iOS.
Expected behavior
The sticky headers should scroll along the content and only stick when the header is fully collapsed. An alternative would be to add support for SectionLists.
Screenshots (if applicable)
RPReplay_Final1613562676-2.mov
The text was updated successfully, but these errors were encountered: