Worked without a problem in last alpha release
Thanks - Any and all help appreciated
This has broken a significant amount of my code. I'm replacing them all with a binding to the "vclick" event, but I'm not happy about this change.
@forrest Agreed, I just changed all bindings to vclick and now my test Android (2.3) ajax navigation is broken. The vclick event is not being caught and the page is being requested as normal. Changing back to using click for everything. Let you know how it all goes.
I am finding a few problems in Android ajax navigation in 2.3 as of the Beta release. In order for ajax navigation to work consistently and to be able to use 'click' events you have to set $.mobile.useFastClick = false. Also look out for this guy, #1904.
Please see this thread for more info: http://forum.jquery.com/topic/beta1-onclick-does-not-work-on-iphone
I'm personally finding that for links it only fails on iphones, and only when href='#'. However I did notice that onclick wasn't working for divs.
You can turn off $.mobile.useFastClick and your click events will work again, but there will be a delay on iOS and other touchscreen devices. Ideally, you'd switch to using vclick in your code to speed up the responsiveness.
BTW - you need to use latest instead of beta 1 if you want to disable this feature.
I can confirm that turning off $.mobile.useFastClick does not affect this issue in beta1.
Did you try latest? There was an issue in beta 1 that made turning this off not work.
How and when are you turning off $.mobile.useFastClick? There was a bug where toggling that option didn't do what it advertised. This is why Todd said you need to try the latest.
No, I haven't tried it yet, and we're overbudget on our jquery mobile upgrade task, so we cannot afford to upgrade again at this time :(
The workaround we found is working well enough for now:
Edit: Had to deform the a tag to keep markdown from making it an actual link
This is now fixed in master.
Jqm beta2 is stable ... switch to beta2