tapping on list item while in inertia scroll gives random results

[egolts]

using 1.0-b4-rc, on mobile safari. start a scroll on a long list with a gesture, let it scroll via inertia, and then tap a list item while it is still scrolling. The expected behavior would be that the scrolling would stop, and then the user would have to tap on the item again to highlight it. Actual behavior is a seemingly random item is selected instead. This is especially problematic if the list items link to other pages, thus giving the user a page they did not intend to see.

If one waits until the scroll stops, then highlighting/linking to new page works as expected.

EDIT:

Just discovered I was using useFastTouch: true. Setting it to false fixes the incorrect linking, but incorrect list items are still highlighted. I've removed background color changes for .active list items as a stop-gap.

[thomasyip]

Is the device an Android? It might be a Zepto's touch.js bug, because we now depends on them on touch stuffs.

If applicable, removing the active class might be a better workaround.
$('.active').removeClass('active')

[egolts]

It’s in ios, using the jquery version. (both ios 5.1 and 6 exhibit the behavior). I’ll give the workaround a try.

[thomasyip]

We reused Zept's touch.js for jQuery. If you use jQuery, you might want to try jquery-jqtouch2.js, which might be better in some situations.

[egolts]

tried the jquery-jqtouch2.js - the app just became a blank black screen. So used it along with the latest source and although the app appeared, much of its' functionality became buggy - double animations, scrolling freezes etc. To use the latest version of the app, all I have to do is grab the versions from master branch in /src right? Just making sure before I give up and stick to the release candidate version instead.

[thomasyip]

All css and js must be updated as well.

There are animation fixes that affected both files.

[egolts]

updated all files - the new version seems to fix the issue when useFastTouch = false. The problem remains when fastTouch is enabled however, but I understand this is an experimental feature. Thanks for the help & info.

[thomasyip]

@egolts, thanks for the update. I think it is a real bug in zepto's touch.js.

I am reopening this to remind myself to file a bug on zepto.