User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36 Firefox for Android Steps to reproduce: 1) Go to https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete 2) Try to enter a zipcode in the "Enter a location" search input Actual results: There are 2 issues 1) Google Autocomplete should show suggestions as you start typing the zipcode. It doesn't until one types a "space" or "comma" after the 5 digit zipcode. 2) When the suggestions do show up (after typing space or comma), you cant choose the first suggestion. As you tap on it, the cursor moves back to the search input. You can however choose the second or third suggestion correctly. Expected results: 1) Suggestions should be displayed as a user starts typing the keywords e.g. "022" should start displaying suggestions for Boston zipcodes 2) Use should be able to select any and all of the suggestions. Problem #2 as you can tell is extremely problematic and very frustrating for the user. We've had received several complaints about this. We have confirmed this on Firefox version 36.0.2 on Samsung S4 running Android 4.4.2.

This issue was posted on StackOverflow and a decent workaround for Problem#2 has been identified. Thought I will update it here for the benefit of other users. http://stackoverflow.com/questions/29174957/google-places-autocomplete-plugin-isnt-working-in-firefox-android Still looking for a way to address Problem #1. One guess is that the key event is not triggering on Firefox Android - http://stackoverflow.com/questions/14194247/key-event-doesnt-trigger-in-firefox-on-android-when-word-suggestion-is-on

I was able to reproduce the second issue in Nightly for Firefox Mobile 46.0a1. I was unable to reproduce the first of the two issues. Can you try and see if subsequent updates on Android has since solved this issue? Thanks.

Hi Grover, Thanks for looking into this. I tried this again with the latest version of Firefox android and agree with you that problem #1 seems to be resolved. As you mentioned, problem #2 still exists but with my CSS workaround it should be alleviated!

We are new to triaging this. Our team came to a consensus that this should go to Plug-Ins as we are trying to clean up Untriaged bugs. Please correct this if this is in the wrong place. Thanks.

Plugins on Firefox for Android would mean that this is a Flash issue. I don't believe that to be the case.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.