Closed Bug 644150 Opened 13 years ago Closed 5 years ago

Tapping on arrows in "Find in Page" will dismiss the virtual keyboard

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

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: xti, Unassigned)

Details

Build id : Mozilla/5.0 (Android;Linux armv7l;rv:2.2a1pre)Gecko/20110323
Firefox/4.0b13pre Fennec /4.1a1pre
Device: Sony Ericsson Xperia X10
OS: Android 2.1 update 1

Steps to reproduce:
1. Open Firefox App
2. Browse to www.mozilla.com/en-US/firefox/features
3. Tap on "Find in Page"
4. In search field type "firefox"
5. Tap on down/up arrow

Expected result:
Tapping on arrows will close the virtual keyboard. It will be up only when Search field will pe tapped again.

Actual result:
The virtual keyboard is displayed as long as you don't tap outside of the
arrows.

Note:
This is a feature request.
In my opinion the keyboard should stay up when we are in portrait and should go while in landscape.
(In reply to comment #1)
> In my opinion the keyboard should stay up when we are in portrait and should go
> while in landscape.

I disagree. For find-in-page, when I start tapping the next/prev we should assume the user has changed focus to searching the page, not typing. Hiding the vkb gives more visual space to search for "found text". If the user wants to switch back to changing the search string, they can tap the searchbox
(In reply to comment #2)
> (In reply to comment #1)
> > In my opinion the keyboard should stay up when we are in portrait and should go
> > while in landscape.
> 
> I disagree. For find-in-page, when I start tapping the next/prev we should
> assume the user has changed focus to searching the page, not typing. Hiding the
> vkb gives more visual space to search for "found text". If the user wants to
> switch back to changing the search string, they can tap the searchbox

My point is mostly:
 - There is enough space on portrait to not care about that
 - This will allow us to remove the Find in page arrows in portrait mode the same way planned for the Form Assistant (which make me thing about a new question for that: What to do in landscape mode for it? show the arrows? bug 636339)
(In reply to comment #3)

> My point is mostly:
>  - There is enough space on portrait to not care about that

I don't agree. it's only half a screen.

>  - This will allow us to remove the Find in page arrows in portrait mode the
> same way planned for the Form Assistant

Using "next" on the vkb will move between focusable widgets in Form Assistant. Find-in-Page does not jump between focusable widgets. It's not the same IMO.
(In reply to comment #4)
> (In reply to comment #3)
> 
> > My point is mostly:
> >  - There is enough space on portrait to not care about that
> 
> I don't agree. it's only half a screen.

Sounds enough to me but we probably need more opinion, my hawk eyes could be misleading :)

> 
> >  - This will allow us to remove the Find in page arrows in portrait mode the
> > same way planned for the Form Assistant
> 
> Using "next" on the vkb will move between focusable widgets in Form Assistant.
> Find-in-Page does not jump between focusable widgets. It's not the same IMO.

hmm, my plan was to override the default behavior for the Form Assistant since we want to ignore some elements whle navigating, I was thinking of doing the same thing here (if it is possible). 
I don't think users will see the focusable point.
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.