SaintFlipper

Thank you @baltedewit and @hreinnbeck. As you say we can hide the page in some way such as setting opacity=0 until play() is called, and I will do that. I...

Hi, the new #8 seems to change the behaviour but not quite fix it: a) It still results in duplicate items when scrolling back to the top (see image) b)...

Thanks for that; my previous logic for handling out-of-range items explains the different behaviour of the stand-alone case, but not the "bouncing range" data source request or the difficulty scrolling...

I'm not seeing a big difference from the previous version. Using http://jsfiddle.net/q4xstonz/1/ and with the results pane 6 items wide I still see the "bouncing data source range" behaviour (see...

Hi Michael I know you were asking @nikita for this, but my fiddle at http://jsfiddle.net/q4xstonz/1/ also shows unexpected behaviour: a) Set the result pane to 6 images wide then scroll...

The duplicate items had a different cause (handling the edge case when the data source requested items < 1), but v1.3.1 still showed the problem with the displayed items jumping...

My apologies, no. I had inferred from the code comments that this was still v1.3.1. On 28 August 2015 at 18:47, stnash [email protected] wrote: > Does your JSFiddle incorporate the...

Updated the fiddle: http://jsfiddle.net/q4xstonz/2/ to use the updated ui-scroll.js ( https://raw.githubusercontent.com/ardas/ui-scroll/6080a88993c949d894c60c8521b0cf8d14b2ebec/dist/ui-scroll.js ). The updated ui-scroll greatly improves the behaviour and items no longer move around within each row (so the...

Hi Matthias That's a very useful observation, which hopefully might help the developers find a longer term solution to this problem. It would be helpful if you could update the...