User Agent: Mozilla/5.0 (Android; Mobile; rv:29.0) Gecko/29.0 Firefox/29.0 (Nightly/Aurora) Build ID: 20140203030203 Steps to reproduce: There's a bug/design flaw with auto-focusing search fields that highlights this, but attempting to click back to dismiss the drop down will navigate back a page which is contradictory to standard Android behaviour. Back should dismiss the keyboard, then the drop down and then navigate back a page.
The easiest example would be to simply open bugzilla (say this bug) click the search field at the top and then click the back button to try and close said drop down (of previous search terms).
The first tap into the search field (GeckoEditable) does focus it, drops down the (suggestion box? options? ?terminology? ...) and opens the IME https://www.dropbox.com/s/pkzr2lp5ol7lhtr/Screenshot_2014-02-09-12-10-12.png Tapping the back button dismisses the IME/softkeyboard, but leaves the editable focused, and the drop down suggestions still available. I would think this is correct. https://www.dropbox.com/s/hxzmp0yh4bdunt3/Screenshot_2014-02-09-12-13-33.png Tapping into white space on the page, say under the "Tracking fields", causes the editable to lose focus, and the dropdown to dismiss. I still don't see an issue ... further clarifications will help me.
Well depending on what page you're on, the white space may take you away from the page. Also there's an argument for UX consistency as traditional dropdowns (i.e. Platform above) require back to dismiss.
You need to log in before you can comment on or make changes to this bug.