Warning against using the fastclick package

elie · December 30, 2016, 12:45pm

Using the fastclick package will mean that select's will stop working on Chrome mobile.

You can read more here:

And here:
https://productforums.google.com/forum/#!topic/chrome/Q4Rt6d0C4Qo

I just spent hours trying to figure out why selects haven’t been working on my site, and finally found out that this package was the issue.

Also you probably don’t want to use it since:

As of late 2015 most mobile browsers - notably Chrome and Safari - no longer have a 300ms touch delay, so fastclick offers no benefit on newer browsers, and risks introducing bugs into your application. Consider carefully whether you really need to use it.
https://github.com/ftlabs/fastclick/commit/4e409926198147f24a49c293923d2a2a047c3774

waldgeist · December 30, 2016, 9:47pm

Thanks for the info. At least it is possible to disable fastclick on certain user interface elements by adding the needsclick class. I had to do this to use typeahead.js on iOS. By the way: Meteor includes fastclick by default, it’s part of the mobile-experience package:

github.com

meteor/meteor/blob/devel/packages/mobile-experience/package.js#L14


summary: 'Packages for a great mobile user experience',
documentation: 'README.md'
});


Package.onUse(function(api) {
api.imply([
  // A nicer appearance for the status bar in PhoneGap/Cordova apps
  "mobile-status-bar"
], "web.cordova");


api.imply([
  // Show a nice splash image while your PhoneGap/Cordova app's UI is loading.
  // Doesn't do anything without Cordova, but we include it everywhere so you
  // don't need a ton of if statements around your LaunchScreen calls.
  "launch-screen"
]);
});

elie · December 31, 2016, 1:33am

Well it only adds it for cordova.