You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When optimizing webstuff for mobile, we need to get around the 300ms delay by adding fastclick to our buttons. When the same page gets viewed on a desktop browser usually onclick handlers work better, because they are not selecting any text when pressing multiple times (desktop browsers interpret this as doubleclick to select text near the cursor).
The text was updated successfully, but these errors were encountered:
This sounds like a good plan. Any ideas what would be the best way to test for a mobile vs desktop browser? It would also be good to see how Chrome for Android and Windows Phones react to this.
When optimizing webstuff for mobile, we need to get around the 300ms delay by adding fastclick to our buttons. When the same page gets viewed on a desktop browser usually onclick handlers work better, because they are not selecting any text when pressing multiple times (desktop browsers interpret this as doubleclick to select text near the cursor).
The text was updated successfully, but these errors were encountered: