[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 to work
1. CustomEvent supports 'detail' property, not 'details'
1. Now registering the custom event in recentlyDispatched instead of original one to avoid the need for iteration over all touches when comparing targets
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 event and our touch event.