[FastClick] fixes #109 by comparing additionally coordinates with previous event

This pull request contains mutiple fixes:

1.  check if touch events are supported, if not there is no need for click handler
1. CustomEvent supports 'detail' property, not 'details'
1. Now registering the custom event in recentlyDispatched instead of original one to be able to check if default has been prevented by user
1. _sameTarget function compares if targets are actually the same as it was before, but it compares additionally the screenX and screenY coordinates to cover cases where  the target could have changed within 300ms. It uses positionThreshold because I saw sometimes insignificant differences between coordinates of click and touch events.
1. multi touch should not lead to a click
1. call preventDefault on delayed click event if user prevented default on custom one