4 ms·
What you are experiencing might be down to the browser waiting for a double tap when you tap on links and buttons. Google produced an article on implementing fa
by fiznool 15y ago
What you are experiencing might be down to the browser waiting for a double tap when you tap on links and buttons. Google produced an article on implementing fast buttons which describes this phenomenon: http://code.google.com/mobile/articles/fast_buttons.html http://code.google.com/mobile/articles/fast_buttons.html
From the article:
' ... mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap. For most buttons we are developing we know that there is no double click behavior that we want to handle, so waiting this long to start acting on the click is time wasted for users. '
The article goes on to discuss how to mitigate against this problem. jQuery Mobile's solution is to use virtual events to listen for touch events rather than mouse clicks. Try listening for vmouseup instead of vclick, this could solve the issue. See http://jquerymobile.com/demos/1.0.1/docs/pages/page-scripting.html http://jquerymobile.com/demos/1.0.1/docs/pages/page-scriptin... for more details.
- deleted 15y ago[deleted]
- untog 15y agoIt isn't that- I've looked into it myself. The delay seems to occur somewhere between the pagebeforeshow and pageshow events- so by that point the click action is definitely already registered. But there must be some function call that slows the whole thing down, interestingly, it doesn't on the iPhone simulator, so presumably it's relatively CPU intensive.