There's currently an issue with ios devices, they currently fail when scrolling.
The culprit is this part:
// if(element.scrollTop != previoustop) {
// reject("interrupted");
// return;
// }
I haven't out how to fix, but the issue is that 'previoustop' variable is often not equal to 'element.scrollTop'. My gut feeling is that ios smooths scrolling by default, which would mean that the 'element.scrollTop' may move slightly by itself.
There's currently an issue with ios devices, they currently fail when scrolling.
The culprit is this part:
// if(element.scrollTop != previoustop) {
// reject("interrupted");
// return;
// }
I haven't out how to fix, but the issue is that 'previoustop' variable is often not equal to 'element.scrollTop'. My gut feeling is that ios smooths scrolling by default, which would mean that the 'element.scrollTop' may move slightly by itself.