senchalabs/jQTouch — Issue #302: tap is disabled when navigating to same page
Author: mattpenner
Created: 2011-10-20 17:42:55+00:00
State: open

When navigation starts the process (roughly) is to start navigation (which disables tap ability), find the page, process it and then end navigation (which re-enables tap).

If the page is the current one it stops the process and never proceeds to the end navigation code, so tap is permanently disabled.

I found it due to a bug in my code (A login screen first is rendered with a "current" class but this class remains if the page is reloaded due to an invalid login. My fix is to not set the "current" class if it is an AJAX call), however, I'm sure this might hit someone else in a legitimate scenario.