707350 - Hardware Keyboard return gives a space instead of a return when using Swiftkey X

Status: VERIFIED FIXED

(Firefox for Android Graveyard :: General, defect, P2)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

1. switch the ime to Swiftkey X Trial
2. launch fennec
3. click in the URL bar
4. type in www.google.com using the hardware keyboard and hit return

Expected: www.google.com
Actual: a space after www.google.com

Note:
Droid Pro, 2.3, Swiftkey X trial, Nightly 20111202

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

in a plain text field it doesn't do anything.  If a submit button is associated with a text field then it will submit the form as expected.  In a text area field, it will move to the next line as expected.

See test page at http://people.mozilla.com/~nhirata/html_tp/formsninput.html

Comment 2

[Alex Pakhotin (:alexp)]

I cannot reproduce the issue as described, though I see bug 705939 more consistently, I think. Also there are weird issues with misplaced characters entered in the Google search box and other edit fields on the Web pages when Swiftkey X is set as default.

Comment 3

[Kevin Brosnan [Ex-Mozilla]]

I can reproduce this using my g2 and Swiftkey from the market.

Comment 4

[Alex Pakhotin (:alexp)]

I've just realized that the Droid Pro, which I test with, has Android 2.2.1 - probably that's why I cannot reproduce this issue. As mentioned earlier I always see bug 705939 though. I wonder if it's possible to upgrade being outside of Verizon network.

And everything works fine on the Droid 3.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Yes, It's possible to upgrade the Droid Pro to Android 2.3; set the network to use CDMA and wireless network.  It should trigger the update.

Comment 6

[Alex Pakhotin (:alexp)]

I still could not reproduce this issue on the Droid Pro with Android 2.3.3 - faced bug 705939 instead. Hope the fix for that bug will fix this one as well.

Comment 7

[Alex Pakhotin (:alexp)]

Naoki, Kevin, could you guys still reproduce this issue with the latest builds?

Comment 8

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

No I could not reproduce this particular issue.  Should I close this as WFM?

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

( build 20120109 Nightly)

Comment 10

[Alex Pakhotin (:alexp)]

(In reply to Naoki Hirata :nhirata from comment #8)
> No I could not reproduce this particular issue.  Should I close this as WFM?

So it was actually fixed by the bug 705939.

Comment 11

[Alex Pakhotin (:alexp)]

Naoki, could you please test the Aurora and if it works there, set status-firefox11=fixed for this bug?

Comment 12

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Verified 20120109 Nightly, Verified 20120110 Aurora