Increase infinite messages scroll distance

[j4hangir]

I suggest the fetch-messages occur as soon as the user is approaching the end of list rather than actually reaching it. At the moment the function's called only when user's actually reached the top, which in turn will always lead to a little lagging xp.

This distance could be halved, or even be customized by a approaching prop, e.g. fetch-distance=0.5, as in the user is half-way of a full-scroll to reaching to the top, whichever better.

A default number might also be preferred and perhaps only a boolean to toggle it.

[antoine92190]

I agree the scrolling distance would be better if increased as in versions < 0.6.5, but then the scroll behaviour is very unpredictable (especially on mobile devices).
I will try to improve that, but it will take some time as it may lead to a lot of refactoring

[j4hangir]

I actually had a feeling it was prefetching on 0.6.3, I guess that got changed in 0.6.5?

In my imagination it's just a matter of calling fetch-messages earlier, I gotta read the code to find out why it might cause a lot of refactoring.

[antoine92190]

Yes it was the case in versions prior 0.6.5. Calling fetch-messages earlier is not difficult, but making the scroll stable on all browsers and devices is. For some reasons, scroll becomes jumpy when we start adding DOM elements without scrolling to the very top before.

[antoine92190]

Prop added in 9c72f2b