Response title
This is preview!
Yes, I understand that. It is a webkit issue. It's to allow for the possibility of a double-tap. I feel it really should be a webkit option to disable it.the 300ms isn't introduced by JQM from what I understand.
Hello,
yep, jQueryMobile removed the useFastClick-Property but kept the underlying events. I'm using this code to bind my links (removing the delay):
$('#aLinkArtStatDetail').bind("vclick", function (ev) {
// Do Some stuff
ev.preventDefault();
});
See http://jquerymobile.com/demos/1.0.1/docs/api/events.html for more details.
Best Regards!
Nice find!!
(cept I think we on the wrong thread lol)
Any help that anyone can provide would be extremely appreciated. I've lost several days of coding due to this one issue.What I end up doing is binding to "touchend" and making sure I put a preventDefault so that underlining click doesn't trigger (causing a double trigger). It seems to work pretty well for simple interfaces.
© 2013 jQuery Foundation
Sponsored by and others.