Closed Bug 720868 Opened 12 years ago Closed 3 years ago

Back/Cancel buttons in Tips dialog for Swype keyboard dismiss awesomebar

Categories

(Firefox for Android Graveyard :: General, defect, P4)

11 Branch
ARM
Android
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: myk, Unassigned)

Details

(Whiteboard: [VKB])

My Samsung Galaxy S phone is set to use the Swype keyboard, which sometimes pops up a Tips dialog box (in particular, when a word I enter is "'hidden' by [a word] that was previously added to your Swype dictionary").

When I dismiss the dialog while entering text into the awesomebar, I expect Fennec to allow me to continue entering text into the awesomebar, but instead it dismisses the awesomebar, forcing me to start over again.

Steps to Reproduce:

1. configure your phone to use the Swype keyboard and start Fennec;
2. tap in the location box to open the awesomebar (Swype keyboard will appear);
3. long press the Swype key in the bottom-left corner of the keyboard (keyboard will disappear, Tips dialog will appear);
4. press Cancel button in dialog or phone's Back button.

Expected Results: awesomebar remains visible, keyboard reappears.

Actual Results: awesomebar gets dismissed, keyboard does not reappear.
Whiteboard: [VKB]
Priority: -- → P4
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: 3 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.