Swiping left or right with triggerOnTouchLeave on Android Chrome browser causes the script to get stuck in a weird state.
Firefox on Desktop doesn't have this problem. Not sure on any other browsers.
The next swipe fails to trigger swipeStatus during swiping, and then always fires either swipeLeft or swipeRight depending on the last swipe. (So you're forced to swipe 2 times in the same direction.)
I wasn't able to really get to the root cause, however re-loading the script fixes it. Ie, after a swipeLeft. do something like:
$("#thing").swipe("destroy");
$("#thing").swipe( { ...... } );
Swiping left or right with triggerOnTouchLeave on Android Chrome browser causes the script to get stuck in a weird state.
Firefox on Desktop doesn't have this problem. Not sure on any other browsers.
The next swipe fails to trigger swipeStatus during swiping, and then always fires either swipeLeft or swipeRight depending on the last swipe. (So you're forced to swipe 2 times in the same direction.)
I wasn't able to really get to the root cause, however re-loading the script fixes it. Ie, after a swipeLeft. do something like:
$("#thing").swipe("destroy");
$("#thing").swipe( { ...... } );