tony said:

Hello,

Thank you for the recommendations.

This feature should be carfully checked and corrected.

Best Regards

Tony

Just wondering what the progress on this bug is?

I found it still has not been addressed in the 3.8 demo so I have manually edited in 3.7.2 as per initial suggested fix and its all working ok (as far as I can tell).

For those wanting to hack the minified version.. just search for “===undefined||” and you will find a line with the same logic but (naturally) different veriable names eg:

c.lastpage===undefined||parseInt((s+p+h-1)/h,10)<=c.lastpage

Thanks

Hi Frode,

I have not seen this behaviour when experimenting with scroll: 1.

I use a default definition like this: