967417 - Back should close drop down before navigating backwards

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: General, defect)

Description

[Paul [pwd]]

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.

Comment 1

[Aaron Train [:aaronmt]]

Example URL?

Comment 2

[Paul [pwd]]

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).

Comment 3

[Mark Capella [:capella]]

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.

Comment 4

[Paul [pwd]]

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.

Comment 5

[miralobontiu]

Hi,

I cannot reproduce the issue.

Tested with:
Browser / Version: Firefox Mobile Nightly 63.0a1 (2018-07-24)
Operating System: HTC 10 (Android 8.0.0)

Could you download the latest Nightly and retry?

Thank you!

Comment 6

[Paul [pwd]]

It appears to have been fixed by another bug. I'm unsure as to which one. While this should've probably been duped over to that bug, I'll mark as invalid.