Turns out I was optimizing for a use case we don't really have -- this tinkering with recognizers was enabling us to have a) fast single-clicking and b) prevent single tap events from firing on a doubletap.

However, I'm not seeing any clear way, with recognizer configs or hammer-time.js, to enable that behavior without incurring a single click delay when recognizing doubletaps.

So, I'm clearing out these attempts at a workaround; the resulting behavior is:

• fast single click when no doubletap handlers are registered;
• a doubletap handler, when registered, works as expected;
• single clicks are fired on the way to a doubletap.

If we need doubletaps to not fire single click events, we need to find a way to enable that without incurring a single click delay. react-map-gl adds a doubletap handler and we don't want to slow down clicks.