-
Notifications
You must be signed in to change notification settings - Fork 24k
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
ListView sticky headers are offset when RefreshControl is active #5405
Comments
Hey samuelkraft, thanks for reporting this issue! React Native, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
|
Thanks for reporting this, I just submitted a PR to fix it! |
Thanks! Let's hope for a merge soon 👍 |
There you go :) |
Yay! 🎉 |
…freshing Summary: When scrolling while RefreshControl is refreshing the sticky headers are offset by the height of the UIRefreshControl. This simply removes the height of the UIRefreshControl while it is refreshing and fixes the problem. You can repro the bug using this example in UIExplorer by doing a pull to refresh and scrolling the ListView immediately after. https://gist.github.com/janicduplessis/26b4f2758e90b2aa1620 Fixes facebook#5405 Closes facebook#5517 Reviewed By: svcscm Differential Revision: D2895623 Pulled By: nicklockwood fb-gh-sync-id: 81df36cccfc3e7b973c2be78565f8b8408c9fc12
I think this regressed somewhere along the way. |
Yup, this is still present in 0.34 |
@janicduplessis should this issue be re-opened? Or is there a new issue somewhere? |
Still present in 0.38 |
Same issue in 0.40 :/ |
Same problem in 0.42.0 :/ |
same problem here |
When using a ListView with "renderSectionHeader" together with RefreshControl the sticky headers will be offset during refreshing. To reproduce pull down to refresh and then scroll back up before the refresh finishes. This is an issue on both 0.17 (onRefreshStart) and 0.18 (RefreshControl).
Gif:
The text was updated successfully, but these errors were encountered: