-
Notifications
You must be signed in to change notification settings - Fork 13.4k
InfiniteScroll and ensuring there is "enough" data #6341
Description
Short description of the problem:
I was working on an application that made use of InfiniteScroll. I did most of my testing in the browser before switching to the iOS emulator. I noticed that when I switched, I no longer had enough data to "fill" the view. Why? I was using a relatively small dataset (10 items) that just so happened filled the view post on the browser and not the emulator.
Now to be clear, I think 10 is too small. I think normally you would want 20-50 items so the user can scroll a bit before InfiniteScroll fires off a request for more data.
So my question is:
Would not having enough items in the view port cause InfiniteScroll to never fire since you can't scroll down to get more?
If so, we should document this. I understand that it may be bad to say, "You should always use 20" since obviously it won't be appropriate for all situations, but the docs should talk about how you want to provide enough to fill the viewport for various devices.