Closed
Bug 600441
Opened 15 years ago
Closed 15 years ago
[regression] Escape key goes back in history when Form Helper is opened
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(fennec2.0b2+)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | 2.0b2+ | --- |
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
Attachments
(1 file)
1.59 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Form Helper is not a popup anymore (and so will be Find Helper in a few) and because of this if VK_ESCAPE is called we're going back in history instead of dismissing the helper.
Steps to reproduce:
* launch fennec
* go to google.fr
* click on the google's textbox
* hit the back arrow of your Android device hardware keyboard or hit ESC on desktop
Actual results:
* fennec goes one page back into history and dismiss the form helper
Expected results:
* fennec dismiss the form helper
Attachment #479271 -
Flags: review?(mark.finkle)
Comment 1•15 years ago
|
||
Comment on attachment 479271 [details] [diff] [review]
Patch
Man, the handleEscape method is ever growing...
Attachment #479271 -
Flags: review?(mark.finkle) → review+
Updated•15 years ago
|
tracking-fennec: --- → 2.0b2+
Whiteboard: [fennec-checkin-postb1]
Assignee | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Comment on attachment 479271 [details] [diff] [review]
> Patch
>
> Man, the handleEscape method is ever growing...
yeah, this is moslty because the way we handle popups, dialogs, panels, ... sucks. At some point (after 2.0) we need to do some code cleanup and find a new way of doing it :(
Assignee: nobody → 21
Comment 3•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [fennec-checkin-postb1]
Comment 4•14 years ago
|
||
Form Helper feature is not available anymore on the latest Nightly build.
--
Mozilla/5.0 (Android;Linux armv7l;rv:9.0a1)Gecko/20110912
Firefox/9.0a1 Fennec/9.0a1
Device: Samsung Galaxy S
OS: Android 2.2
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•