Hitting the return key should dismiss the virtual keyboard

NEW
Unassigned

Status

Firefox for Android Graveyard
General
7 years ago
7 years ago

People

(Reporter: Paul [pwd], Unassigned)

Tracking

Trunk
ARM
Android

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110524 Firefox/6.0a1
Build Identifier: 

Pressing enter in a search <input> box does nothing, it should start a search or at the very least exit the box (in landscape) and return the user to the page.

Reproducible: Always
(Reporter)

Updated

7 years ago
OS: Other → Android
Hardware: Other → ARM
What do you call an <input> box? Can you give examples?
(Reporter)

Comment 2

7 years ago
STR:
1/ Put phone in landscape
2/ Click on an <input> (single line text box)
3/ Write some text
4/ Click enter

Expected Results: You should be taken back to the page out of the editor.

Actual Results: You're left within the text editor.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Enter in search box should invoke search → Hitting the return key should dismiss the virtual keyboard
Just as a use case : What about forms that have multiple input text boxes?
http://people.mozilla.org/~nhirata/html_tp/formsninput.html

Personally, I would find it annoying if I hit return, had to click on a field for input and the VKB was animating back and forth every time.  Not sure how others feel.
(Reporter)

Comment 4

7 years ago
if you hit enter in a normal input box it submits the form, why would you ignore convention completely on mobile?
It depends on the text fields.  see the test page. that I linked in Comment 3.  First text boxes doesn't submit the form, the username field will submit the form.  This occurs even in mobile.

Personally, I think mobile conventions should be slightly different because it's a different type of user interface (touch interface/typing on a mobile device is more of a pain IMHO) with different limitation (such as size/spacing/memory, etc.).  that's just my belief though.
(Reporter)

Comment 6

7 years ago
Please note this bug is about input boxes and not textareas. also note that the slightly different convention is exiting the input box and not submitting the form.
Well, perhaps it's my misunderstanding, but I am not sure what you are referring to when you state input boxes based on your last comment.  Can you give an example of some html code?
(Reporter)

Comment 8

7 years ago
(In reply to comment #7)
> Well, perhaps it's my misunderstanding, but I am not sure what you are
> referring to when you state input boxes based on your last comment.  Can you
> give an example of some html code?
To use html from this very page:

<input id="status_whiteboard" name="status_whiteboard" class="text_input" value="" size="40"> = Dismiss virtual keyboard.

<textarea name="comment" id="comment" rows="10" cols="80"></textarea> = Create new line within editor.
I apologize.   I see your point in landscape where you can't see anything.  I suppose it was my fault for reading too fast.
(In reply to comment #9)
> I apologize.   I see your point in landscape where you can't see anything. 
> I suppose it was my fault for reading too fast.

Not completely your fault, i was myself thinking about it silently to be sure to understand the point.
You need to log in before you can comment on or make changes to this bug.