autocomplete: virtual keyboard not appearing on mobile/android

[matthesrieke]

Bug:

CodePen Demo which demonstrates the issue:

https://codepen.io/anon/pen/mKjXMN (default CodePen created from the "Floating Label" example in https://material.angularjs.org/1.1.9/demo/autocomplete)

Detailed Reproduction Steps:

1. Open up https://material.angularjs.org/1.1.9/demo/autocomplete on Chrome in Android (tested with two Android 7.0 stock ROMs (Huawei Honor 9 and HTC One M9)
2. Scroll to the floating label example and tap the "Favorite State" input
3. Type something that matches (e.g. "Ari")
4. Tap outside of the input and suggestions
5. Wait 2-3 seconds
6. Tap again into the "Favorite State" input

What is the expected behavior?

The Virtual Keyboard should open up when tapping into the input field

What is the current behavior?

The Virtual Keyboard does not appear most of the time. When tapping outside and again inside within a short period (< 1 second) the virtual keyboard more reliably appears.

What is the use-case or motivation for changing an existing behavior?

Bug.

Which versions of AngularJS, Material, OS, and browsers are affected?

• AngularJS: 1.6.7
• AngularJS Material: 1.1.9
• OS: Android 7.0 stock ROMs (Huawei Honor 9 and HTC One M9)
• Browsers: Chrome (Brave also applies)

Is there anything else we should know? Stack Traces, Screenshots, etc.

[Splaktar]

I am not able to reproduce this using a Pixel XL running Android 8.1.0 with Chrome or Firefox. I tried quick pauses and long pauses, but the virtual keyboard appeared almost instantly each time.

Please provide more details on the reproduction and some indication of how this is a bug in AngularJS Material.

[matthesrieke]

Thanks for testing the issue. I can only give you the information I had in my original posting. The one difference I see is the Android version. I can only report it for 7.0 (I do not have other devices at my disposal). I have created a quick GIF showcasing the issue. I can also tell that normal input fields (both common HTML as well as Material inputs) work perfectly fine and always open up the virtual keyboard.

Edit: at the end of the GIF you can see the autocomplete progress bar appearing for a blink of an eye for multiple times. That were the taps on the input field.

[Ruudi-V]

I currently have an analogous problem. The bug was introduced, when i added md-min-length="0" to the autocomplete.

Related code:
https://codepen.io/anon/pen/mjOQRd

Tested on Galaxy Tab Active2, Google Chrome for Android ver 67.0.0.3396.87