Closed Bug 784546 Opened 14 years ago Closed 11 years ago

Steam mobile search provides "Next" action rather than "Go" action on soft keyboard

Categories

(Firefox for Android Graveyard :: Keyboards and IME, defect, P3)

ARM
Android
defect

Tracking

(firefox14 affected, firefox15 affected, firefox16 affected, firefox17 affected, firefox39 unaffected)

RESOLVED WORKSFORME
Tracking Status
firefox14 --- affected
firefox15 --- affected
firefox16 --- affected
firefox17 --- affected
firefox39 --- unaffected

People

(Reporter: mcomella, Unassigned)

References

()

Details

1) Open Firefox. 2) Go to http://store.steampowered.com/mobilestorefront/search 3) Type "counter" into the search box 4) Hit "Next" in the soft keyboard Expected: Search results appear (such as "Counter-Strike") Actual: Nothing happens. After checking with Chrome, it seems the soft keyboard displays the "Next" option rather than the "Go" option. If there are search results present (from previous searches), hitting "Next" will select the first search result momentarily before hiding the results. This can be worked around by not hitting "Next" and letting the search activate by itself over time, however, it is very unintuitive to do this.
mcomella, what device and virtual keyboard are you using? On my Galaxy Nexus running Jelly Bean, Chrome displays a "Go" button on the Steam search page. ICS and JB keyboards seem to display the "Next" button less often than Gingerbread. I believe this is a dupe of bug 708457. These bugs should be fixed if we implement bug 720475.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
(In reply to Chris Peterson (:cpeterson) from comment #1) > mcomella, what device and virtual keyboard are you using? Galaxy Nexus, 4.0.4 (Verizon). I generally use TouchPal in the sliding mode and occasionally Google's Korean IME. I've tested this under TouchPal, the standard Android keyboard, and Google's Korean IME, which all appear with "Next".
Michael, do you see a "Next" button when entering text on this test page (from bug 708457)? https://bug708457.bugzilla.mozilla.org/attachment.cgi?id=597241 I wonder why I see different keyboard behavior than you on my devices' stock browsers. My TouchPal does not have a "Next" button on Gingerbread or JB stock browsers or Chrome. And on my Galaxy Nexus (Jelly Bean), Samsung's default keyboard does not have a "Next" button in Chrome or the stock browser. But on my Galaxy Note (Gingerbread), Samsung's (slightly different) default keyboard *does* have a "Next" button in the stock browser.
(In reply to Chris Peterson (:cpeterson) from comment #3) > Michael, do you see a "Next" button when entering text on this test page > (from bug 708457)? I see a "Go" button on all three IMEs in all three browsers (Chrome, stock, and Nightly). > I wonder why I see different keyboard behavior than you on my devices' stock > browsers. Sorry if I was unclear but I did not mention the behavior on the stock browser. The Steam store shows "Go" on all three IMEs in the stock browser and Chrome while Nightly shows "Next". To be clear, the name of the key is affecting the action it takes: "Go" will submit the form while "Next" tries to move to the next element.
I'm reopening this bug because I misread the original description of the bug. I see now that this bug is about Firefox showing "Next" where other browsers show "Go". I confused it with bug 708457, which was about Firefox *not* showing "Next" when it should. Sorry for the confusion! <:)
Status: RESOLVED → REOPENED
Priority: -- → P3
Resolution: DUPLICATE → ---
This bug is pretty annoying because the keyboard won't allow you to submit your search.
Works for me as expected ("Go" behavior) on Nexus 4 with Android 5.0.1
Closing as WORKSFORME. Thanks for testing, friedger!
Status: REOPENED → RESOLVED
Closed: 14 years ago11 years ago
Resolution: --- → WORKSFORME
I can confirm: on my N7 (4.4) and N4 (5.0), this now works and displays "Go", as per comment 7. Either we, or Steam, did something right.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.