Scroller bug - There are no rows when scroll snaps back

tbarradas

Hello everyone,

I'm not aware whether this is a known bug or not but as it's something that I'm currently having to deal with I thought I should let you know:

When using scroller with server-side data, if you start scrolling up enough to trigger a load then snap the scroll back, by e.g. dropping the click on a different element, there won't be any rows on the table until you scroll up or down enough to trigger another loading. If you do the same while scrolling down the bar behaves a tad strangely but it works correctly for the most part. I haven't tried with local data.

The described behaviour can be seen on the current example page by scrolling to about halfway, waiting for it to load, then starting to scroll up until the loading indicator shows, holding onto the mouse button and moving the pointer left and into the table until the scroll snaps back down, then releasing the click.
https://datatables.net/extensions/scroller/examples/initialisation/server-side_processing.html

I have tested this on chrome 57.0.2987.133, firefox 52.0.1, edge 38.14393.1066.0, IE 11.1066.14393.0

kthorngren

Sounds like a problem I ran into. Take a look at this discussion.
https://datatables.net/forums/discussion/40391/scroller-as-a-console-log#latest

Maybe you just need to get the latest code.

Kevin

tbarradas

Thanks for the really swift answer!

Alas, I went and made sure to get the most recent version from github, while making sure that it had the changes that Allan mentioned to you, and the problem stayed.

tbarradas

I should state that when I said "The described behaviour can be seen on the current example page by scrolling to about halfway, waiting for it to load, then starting to scroll up until the loading indicator shows" I meant scrolling up by clicking on the bar and holding it, no scroll wheel involved at any point here.