Typo: Using FT's FastClick with [Google Maps API]** stops.. etc

The problem seems worse (again iOS6 / iPhone 4S) using a more advanced example:

https://developers.google.com/maps/documentation/javascript/examples/control-options

FastClick: http://mattandre.ws/fastclick/advanced.html
No FastClick: http://mattandre.ws/nofastclick/advanced.html

With FastClick the top right hand side's dropdown does not accept touch input.  (It doesn't do anything)

Nexus 7 has woken up - exactly the same issues.

(No comment was entered for this change.)

Hi Matt,

It's not entirely clear what is needed here to get the libraries to play well together. Looking at the bootstrap change
https://github.com/twbs/bootstrap/pull/6488
it looks like they removed touchstart event listening from their dropdowns altogether. That doesn't seem to be a viable solution for getting interoperation with most libraries. Am I just missing a better solution?

Hi bcke...,

I agree that removing all touch start listeners would not be a good idea but is there a particular reason why the UI buttons need to have touch start listeners on them?  In this case could the buttons not just have click listeners instead?

Thanks,

Matt

Honestly I'm surprised that v3 works as well as it does with FastClick given the number of times we do use touchstart :)

I'm trying to figure out what's happening here. Is there a good example of FastClick working with a library that does use touchstart? Is the problem just that your listeners are clobbering ours, or is the combination of the two just making what appear to be multiple clicks on the elements?

Ok I have had a chance to look into this a bit more.  This isn't caused by onTouchStart, it's caused by what we do onTouchEnd...

The way your dropdown opens & the way labels appear beneath the Map/Satellite buttons seem to have some slightly odd logic - on iOS it *seems* to be some time after touch end...  (I think you're mapping something onto what would be the mouseover event on Desktop, maybe?) and by synthesising a click on the button (rather than letting the touchEnd go through as normal) we seem to be preventing that logic from running.

That's about the limit the diagnosis I can do with minified javascript?  Is there any way we could see the original pre-minified source to debug this further?

Incidentally one thing that I suspect might fix this: if your buttons were <button>s and dropdowns were <select>s (rather than <div>s and, <div>s) our library would not get in the way at all :-).

(No comment was entered for this change.)