Trying to type in the AwesomeBar with the Droid Pro (with hard keyboard) doesn't work. The URL bar simply loses focus when a character is pressed.
I am running into this while trying to use monkey runner
Brian, could you try latest birch and tell me if this still happens. I've just pushed a focus-related fix (bug 697121) which might be related to this bug. Can you see where the focus goes once the URL text entry loses focus?
WFM on droid pro with latest nightly birch.
Yes, I'm still seeing this bug. I don't know where the focus goes - it doesn't look like anything has focus.
After installing a soft keyboard and setting "Input method" to the soft keyboard in the Android settings, the hard keyboard works.
I noticed that I used the simeji IME on the Droid Pro and that's why it worked. On the Droid 2 with the default IME (Multi-touch Keyboard), the hardware keyboard did not work.
I just realized, given bug 698131; the focus is on the first line of the list. The first item is highlighted because it's all white.
using the latest build from birch, I am unable to get this to work :(
Seeing as how this renders the browser completely useless without the ability to invoke a virtual keyboard on such a device (and probably dozens akin), this should have a high priority.
i just experienced this on birch nightly from this morning on my G2, the soft keyboard works fine but i can't type in the URL bar with the physical keyboard. basically commenting to say G2 has the same problem. the focus drops down to the first entry under "All Pages" (it's highlighted).
Confirmed with Motorola Droid 3. Now I've got a phone with keyboard and I'm working on this.
Created attachment 573054 [details] [diff] [review] Fix The TabHost somehow steals the focus from the edit box on keyboard input. The fix is to explicitly request the focus when the awesome screen opens and when the edit box is touched.
Just adding Sriram and Lucas to CC in case something in the Awesombar.java or AwesombarTabs.java is doing the focus thing on purpose. We do things like http://hg.mozilla.org/projects/birch/rev/365da62068e0 and: http://mxr.mozilla.org/projects-central/source/birch/embedding/android/AwesomeBar.java#107 I just want to make sure we aren't fighting code we added on purpose. If we are, we need to make sure we aren't cancelling anything out.
In this case the stealing of the focus happened before any AwesomeBar listeners got called, which made the bug especially difficult to understand.
By the way, I should have mentioned: this bug was not really a regression, but rather an unexpected side-effect of a new feature added in the bug 695307, specifically - the AwesomeBarTabs. JFYI.
(In reply to Alex Pakhotin (:alexp) from comment #17) > By the way, I should have mentioned: this bug was not really a regression, > but rather an unexpected side-effect of a new feature added in the bug > 695307, specifically - the AwesomeBarTabs. JFYI. Just make sure soft keyboard is hidden when switching tabs or whenever the text entry loses focus.
20111109040505 http://hg.mozilla.org/projects/birch/rev/edd8921d5bb8 Motorola Droid Pro (Android 2.3) Filed bug 701018 as another issue with the Motorola Droid Pro
This busted accessing virtual keyboard on landscape: bug 701021, touch input bug 701020, and maybe bug 701018.
I suggest to back out this patch until there's a clean fix for this bug.
why did you reopen this bug? The patch fixed the bug in question. Do not reopen unless there's been a back out
The patch does fix the bug as described, but unfortunately does break the touch mode. :( I tested the basic things with VKB and it seemed to work, but apparently not in all cases. The problem here is with TabHost, which our AwesomeBarTabs is based on. It steals the focus when it shouldn't. It's actually a known issue: http://code.google.com/p/android/issues/detail?id=2516 I used the workaround mentioned there, but apparently it has too many bad side-effects.
Backed out due to VKB regressions. Need another solution.
Created attachment 573761 [details] [diff] [review] Fix v2 OK, this looks like the real fix. The hardware keyboard works, and I don't see any of those issues appeared after the first version.
I guess this is also the reason that it is impossible to use the vkb or the normal keyboard in native Fennec on the Android emulator?
I'm able to confirm this case on 20111111 nightly for testday. Motorola Droid Pro, Android 2.2
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #26) > I guess this is also the reason that it is impossible to use the vkb or the > normal keyboard in native Fennec on the Android emulator? I do have the same issue on the emulator. Very likely related to this problem here, as the symptoms are exactly the same as with android on tegra with USB hardware keyboard attached.
Created attachment 574348 [details] [diff] [review] Cannot type in AwesomeBar URL bar with hard keyboard.
Comment on attachment 574348 [details] [diff] [review] Cannot type in AwesomeBar URL bar with hard keyboard. bzexport fail
20111115055623 http://hg.mozilla.org/projects/birch/rev/6b776bed41d7 Motorola Droid Pro (Android 2.3)
this works on my Android 2.3 G2 in today's nightly as well :)