Closed Bug 701895 Opened 12 years ago Closed 3 years ago

[IME] return key does not cause the urlbar to go to the website using simeji

Categories

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

ARM
Android
defect

Tracking

(firefox14-, blocking-fennec1.0 -)

RESOLVED INCOMPLETE
Tracking Status
firefox14 - ---
blocking-fennec1.0 --- -

People

(Reporter: nhirata, Unassigned, Mentored)

References

Details

(Whiteboard: [testday-20111111], [VKB])

1. download and use simeji
2. start fennec
3. in the url bar using english type in www.google.com
4. hit the return button

Expected: the VKB dismisses and it goes to the website
Actual: the VKB dismisses and you are still at the awesome page

Note:
1. have to turn the device sideways with the VKB up and hit the go button to the right of the input field.

HTC Thrive Testday build
Assignee: nobody → alexp
Whiteboard: [testday-20111111] → [testday-20111111], [VKB]
Priority: -- → P4
This is interesting - looks like the Simeji keyboard is affected by the focus stealing behavior of the TabHost, like the hardware keyboards, but even worse. When Enter is pressed on this VKB, the focus jumps to the tabs below the edit box, but the key event does not go through to the handler implemented in the bug 697773 - apparently the event gets consumed by the TabHost. Not sure what to do here. This seems to be another issue related to the bug 702995.
Depends on: 702995
Behavior acts according to Comment 1 in the tinderbox build.
This issue still appears in Nightly 20120109
Assignee: alex.mozilla → cpeterson
Component: General → IME
Naoki, could you retest this again when you get a chance?
Keywords: qawanted
Hitting return still places the focus into the tabs below the edit box.
Tested : HTC Desire Nightly 3/22/2012
blocking-fennec1.0: --- → ?
blocking-fennec1.0: ? → -
I can reproduce this too easily with Simeji (i.e., https://play.google.com/store/apps/details?id=com.adamrocker.android.input.simeji&hl=en) -- change the input method to Simeji and use Naoki's STR in comment #0
Keywords: qawanted
I believe the AwesomeBar TabHost is stealing focus from the AwesomeBarEditText. Other people have reported similar problems:

https://code.google.com/p/android/issues/detail?id=2516

http://stackoverflow.com/questions/786334/why-is-is-a-tabhost-stealing-focus-from-a-textview-in-android

This bug only seems to affect Simeji. Swype and the Google Japanese Input VKBs are not affeted.
tracking-fennec: --- → ?
Why are we fixing non-blocking bugs right now?
I'm not actively working on this bug. I was just adding some old notes so they will be available when I pick up this bug later.
Priority: P4 → P3
This issue is still reproducible using the STR from comment0 using:
Nightly 18.0a1 (2012-09-30)
Aurora 17.0a2 (2012-09-30)
Devices: HTC Desire Z (Android 2.3.3), Asus Transformer TF101(Android 4.0.3)
Keywords: qawanted
I can repro with Simeji on my Galaxy Nexus (JB).
tracking-fennec: ? → +
Assignee: cpeterson → nobody
Whiteboard: [testday-20111111], [VKB] → [testday-20111111], [VKB][mentor=jchen]
Mentor: nchen
Whiteboard: [testday-20111111], [VKB][mentor=jchen] → [testday-20111111], [VKB]
This bug is old and no more progress for more than 2 years, so I am removing the tracking flag now.
feel free to renominate. 

Thank you !
tracking-fennec: + → ---
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.