ftlabs / fastclick

Polyfill to remove click delays on browsers with touch UIs
MIT License
18.67k stars 3.23k forks source link

Any way to work around issues with Google Places AutoComplete? #316

Open RickStrahl opened 10 years ago

RickStrahl commented 10 years ago

I'm working with Google Places AutoComplete on iOS (8) which pops up a dropdown under a text box dynamically.

The Places Autocomplete is finicky to begin with - it never worked on Windows Phone for example, but when I add fastclick to the page it also fails in iOS , the selections are not triggering an autocomplete update as it should. It seems the tap registers - the dropdown goes away but the Maps API fails to select the actual value.

An example of this behavior can be found here: http://geocrumbs.net/app/#/search

Anyway - any idea how to work around this? I've tried setting class="needsclick" on the container of the textbox and the textbox, but the actual click operation is happening on the dynamically generated dropdown box so I can't easily assign needsclick to that.

FWIW, it appears that it works on even an ancient Android device with Chrome, so at this point it's mainly iOS that's the problem.

matthew-andrews commented 9 years ago

That is strange! I suspect there's something funky going on inside Google's code…

You could consider using selective-fastclick to apply FastClick to just the elements that you know to be safe?