5 ms·
Use at your own risk. On our website it brought a lot of small unanticipated errors in the user interface that we only uncovered slowly. It didn't work in IE8
by Revisor 14y ago
Use at your own risk. On our website it brought a lot of small unanticipated errors in the user interface that we only uncovered slowly.
It didn't work in IE8 out of the box. Some users reported they had to double tap very fast on iPad to actually activate any link (I couldn't reproduce it on my iPad). On some older Android devices it made links and menus behave erratically.
In the end we disabled FastClick completely.
- hayksaakian 14y agoGiven that this library is specifically aimed at mobile browsers, why would you have problems with ie8? Your other complaints seem inconclusive. By default, you're wasting 300ms of most peoples time every time they click, this kind of default automatically puts any standard HTML you do on mobile behind native controls. On android for instance, you should almost never expect your user to double tap as that result is now typically proceed with long presses.
- PStamatiou 14y agoYou can load it conditionally for mobile safari only. IE, something like this (using the lightweight head.js loader): // load fast click if mobile safari if(navigator.userAgent.match(/(iPhone|iPod|iPad)/i) { head.js("js/fastclick.min.js", function() {}); } or include it in your main compressed js assets but only execute if mobile safari
- deleted 14y ago[deleted]
- taf2 14y agosyntax error, missing ) after the if statement. I always do that too.
- mattcg 14y agoI'm sure it won't be too difficult to fix those bugs. What version of FastClick were you using? Were you testing on Android 2? If so I'm working on support for that.