Closed Bug 790974 Opened 12 years ago Closed 4 years ago

VKB is not dismissed when Firefox Menu is triggered

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox16 affected, firefox17 affected, firefox18 affected, firefox21 affected, firefox22 affected, firefox23 affected, firefox24 affected)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox16 --- affected
firefox17 --- affected
firefox18 --- affected
firefox21 --- affected
firefox22 --- affected
firefox23 --- affected
firefox24 --- affected

People

(Reporter: xti, Unassigned)

Details

Firefox 18.0a1 (2012-09-12)
Device: Galaxy Note
OS: Android 4.0.4

Steps to reproduce:
1. Open Firefox for Android
2. Go to google.com (do not dismiss the VKB)
3. Tap on device Menu button and tap on Downloads
4. Type anything
5. Dismiss the VKB and close the tab opened at step 3

Expected result:
VKB is dismissed when Menu button is tapped.

Actual result:
After step 3, the VKB is still displayed on screen.
After step 5, the Google search field is filled with what you have typed at step 4.
This is still an issue on Firefox for Android 21 RC2 on LG Optimus ARMv6 (Android 2.3.4)
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.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.