As a user, I would like common functions to appear on the keyboard when I am typing in specific fields so that I can quickly complete text or perform action on the text box. Acceptance: (Follow visual spec) In multiline text input, far right button in bottom row is the “enter” key which does a line break. In search fields, far right button is a “search” key, which searches for the text in the field. In single line text input or password fields, far right button is “Go”, which completes the input and moves to the next field if applicable. In url fields, the “.com” button appears which will enter .com at the caret. The “/” character is to the left of the space bar and will enter a / at the caret. In email fields, the “.com” button appears which will enter.com at the caret. The “@” character is to the left of the space bar and will enter a @ at the caret. Refer to pp. 17~18 of UX spec in bug 983043

See bug 983043 for the UX spec update.

Added the test cases. - https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-tag=2641

After a discussion with Omega, this feature may not be feasible for 2.0 because, 1. per the p.18 of UX spec in bug 983043, we need to know if the input is in the form, however, so far we don't have that info in Gaia layer. 2. Besides, the better way to do this would be: let the developer be able to specify the "input hint" instead of doing some guessing is O.S level, this is because we could not know what action is associated to that input when the user presses "Enter" key. e.g. When a user inputs a "url" in a contacts app, it may not make sense to change "Enter" to "GO". -- Howie, I'll remove the target milestone first.

Omega, if possible, please help chime in per UX perspective. Thank you.

(In reply to Rudy Lu [:rudyl] from comment #3) > 2. Besides, the better way to do this would be: let the developer be able > to specify the "input hint" instead of doing some guessing is O.S level, > this is because we could not know what action is associated to that input > when the user presses "Enter" key. 2. makes more sense. We will come out some proposal targeting 2.1.

Please see Bug 983043 for latest UX spec.

What's the status of this bug? Is it being covered by multiple bugs out there?

Rudy, do you know the answer to above question?

Not exactly, this is a feature that might need Gecko support, which I already had a brief discussion with Xulei. We could continue the discussion on API/standard we need for v2.2 if this is in UX's priority list.

Let's make a decision on whether or not this should reach 2.2.

Rudy, could you explicitly states what UI changes or API support this bug represents? From comment 0 this bug looks redundant but I am not sure.

There is one statement in comment 0 that we have not implemented: >> In single line text input or password fields, far right button is “Go”, which completes the input and moves to the next field if applicable. And as the UX spec also stated to change the [Enter] key to [Next] for form navigation, which is why I mentioned form navigation in comment 3. I would suggest we keep to the bug for customizable label for the [Enter] key, like [GO], [Done], [Send], and track form navigation with bug 857637.

Firefox OS is not being worked on