removed vclick + click combined event binding, which was in there as a workaround for a not-consistently-occurring bug in Android 2.1. I think the real issue is related to lack of dynamic base tag support, and that occasionally, a relative href click will use default handling in 2.1 and go where it shouldn't (ignoring the base href). Either way, this double binding causes history problems in Safari, so I'm removing it while we search for a better 2.1 workaround. Fixes jquery-archive#1870

Author: scottjehl

js/jquery.mobile.navigation.js

@@ -999,12 +999,7 @@
 		});
 
 		// click routing - direct to HTTP or Ajax, accordingly
-		// TODO: most of the time, vclick will be all we need for fastClick bulletproofing.
-		// However, it seems that in Android 2.1, a click event
-		// will occasionally arrive independently of the bound vclick
-		// binding to click as well seems to help in this edge case
-		// we'll dig into this further in the next release cycle
-		$( document ).bind( $.mobile.useFastClick ? "vclick click" : "click", function( event ) {
+		$( document ).bind( $.mobile.useFastClick ? "vclick" : "click", function( event ) {
 			var link = findClosestLink( event.target );
 			if ( !link ) {
 				return;