-
Notifications
You must be signed in to change notification settings - Fork 73
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
Scrolling fast causes some rows to stay hidden #21
Comments
i also got this issues |
facing same issue |
Same here |
I think it happens only on Section Headers ListView, not sure about it though. |
Does anyone have any updated findings on this? Just found this project. |
@jpdesigndev. This is a known issue. At this point, I'm not sure if the best approach is to fix the existing bug within the existing logic? Or to switch to an interval tree as presented by @rreusser in PR #10 (which I think is pretty cool - but potentially costly). Either way, this really should get fixed. I wish I had more time. |
Thanks for responding. I really appreciate your project. I'm just getting started with iOS and React Native, and it seems I've bitten off more than I can chew at the moment trying to implement Infinite Pages Scrolling. It seems rather simple in native to do, but was hoping to not have to drop down to Obj-C/Swift right from the start. Due to my inexperience in all of this, I, unfortunately, won't be of any help here. |
@sghiassy, is there any update with this bug? |
@sghiassy I can׳t find the correct answer, there are too much comments without clean solution, please assist,Thanks. |
Has anyone figured out a good solution to this? My app has long lists (1000+) so the stock ListView just can't handle it. This works great, except when I scroll quickly or hit the end of the list the rows disappear. |
I notice when I scroll fast that some rows don't get set to be visible again... Also when data is added to DataSource (infinite scrolling) sometimes the first new row is hidden when it should be showing
The text was updated successfully, but these errors were encountered: