Closed Bug 601908 Opened 14 years ago Closed 14 years ago

[VKB] Software Keyboard remains popped up in add-ons manager

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ioana.chiorean, Assigned: vingtetun)

Details

(Keywords: ux-userfeedback)

Attachments

(2 files)

Attached image screenshot
Build Identifier: Mozilla/5.0 (Android; Linux armv7l; en-US; rv:2.0b7pre)
Gecko/20101004Firefox/4.0b7pre Fennec/4.0b2pre 

Device HTC Desire and Motorola Droid 2

Steps to reproduce:
1. open Fennec-> Preferences -> Add-ons
2. Type a term in the search field through the VKB 
3. after entering the work pres enter/ dismiss VKB / tap the results

Expected result:
- the VKB should disappear 

Actual result:
- the VKB should doesn't disappear
I believe this is intended as the designed exit options out of the virtual keyboard are when a user performs an action outside of the virtual keyboard. Naoki, Beltzner what do you think of this issue?
Keywords: ux-feedback
VKB should disappear when panning a list, except for the awesomebar. Might be fixed by bug 592330.

Vivien - is it fixed by bug 592330?
(In reply to comment #2)
> VKB should disappear when panning a list, except for the awesomebar. Might be
> fixed by bug 592330.

I think VKB should _not_ dissapear when panning a list, except for the awesomebar, and so bug 592330 will not fix that.

Ioana issue is because when you enter a search term then press enter the keyboard is still there.
This happen because enter is not useful inside this field who search as soon as a letter is entered. We probably just need to blur the field when the user hit RETURN because in this case it means inputting is finished
(In reply to comment #3)
> (In reply to comment #2)
> > VKB should disappear when panning a list, except for the awesomebar. Might be
> > fixed by bug 592330.
> 
> I think VKB should _not_ dissapear when panning a list, except for the
> awesomebar, and so bug 592330 will not fix that.

You're right

> Ioana issue is because when you enter a search term then press enter the
> keyboard is still there.
> This happen because enter is not useful inside this field who search as soon as
> a letter is entered. We probably just need to blur the field when the user hit
> RETURN because in this case it means inputting is finished

I agree with this idea. Using the RETURN key as a way to say "I am finished typing and want to see my search results" means the VKB should go away. We should blur from the textbox in this case. I think this is should be the convention in any other textbox searches, except the awesomebar - which has it's own rules.
Comment on attachment 481817 [details] [diff] [review]
Patch

Anything more complicated and I would ask you to move the code to ExtensionsView. I don't like putting too much JS in the XUL.
Attachment #481817 - Flags: review?(mark.finkle) → review+
http://hg.mozilla.org/mobile-browser/rev/ad2155d5736a
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
verified FIXED on the Vibrant and Nexus One:

Mozilla/5.0 (Android; Linux armv71; rv:2.0b8pre) Gecko/20101011 Namoroka/4.0b8pre Fennec/4.0b2pre
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
Flags: in-litmus?
Flags: in-litmus? → in-litmus?(nhirata.bugzilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: