Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The reality is that tap events won't work correctly until you actively fix them, and almost all of them can be fixed (including ghost clicks). Fastclick.js does help here a bit, but it's not perfect. We did a ton of work on our end to have a comprehensive tap solution (though some of it is specific to Ionic projects), but could be useful for inspiration for your own project: https://github.com/driftyco/ionic/blob/master/js/utils/tap.j...


Thanks for the link. We also have an in-house solution like fastclick.

The hard part about this is tracking down the long tail of failures, particularly when they affect devices you don't have access to like the Samsung phones I mentioned above. It means we cannot make any changes to the code we already have without risking breaking some users who currently work (and rely on our app; as separate from the users for whom the app has never worked).


Yea, I agree. The situation is annoying, but with Chrome on 4.4 around the bend, I think it's only time before this is a legacy issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: