810249 - Some VKB are not triggered in landscape mode

Status: RESOLVED WONTFIX

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

Description

[Cristian Nicolae (:xti)]

Firefox 19.0a1 (2012-11-08)
Device: HTC Desire Z
OS: Android 2.3.3
Keyboards: SwiftKey 3 Trial, Simeji

Steps to reproduce:
1. In landscape mode, open Firefox Mobile
2. Tap on the URL bar

Expected result:
The Awesomescreen is displayed but the virtual keyboard is not opened

Actual result:
The Awesomescreen is displayed but the virtual keyboard is opened

Comment 1

[Aaron Train [:aaronmt]]

What does this have to do with 3rd party keyboards? The same is true for stock Android keyboard; and the same is true for portrait. What is the bug here? Having the keyboard prompt open has been this way since Fennec 14 so you can type an address. If you mean, switching to bookmarks tab, then this is a dupe of bug 808408.

Comment 2

[Cristian Nicolae (:xti)]

(In reply to Aaron Train [:aaronmt] from comment #1)
> What does this have to do with 3rd party keyboards? The same is true for
> stock Android keyboard; and the same is true for portrait. What is the bug
> here? Having the keyboard prompt open has been this way since Fennec 14 so
> you can type an address. If you mean, switching to bookmarks tab, then this
> is a dupe of bug 808408.

For the Android keyboard, the vkb is not triggered in landscape when going to Awesomescreen. It's triggered just for SwiftKey 3 Trial and Simeji keyboards.

Comment 3

[Aaron Train [:aaronmt]]

I get a the stock keyboard invoked in landscape on my Galaxy Nexus

Comment 4

[(inactive) Jim Chen [:jchen] [:darchons]]

Possible dupe of bug 808666? Although go keyboard IS a 3rd party keyboard.

Comment 6

[(inactive) Jim Chen [:jchen] [:darchons]]

After some debugging, this looks like a bug in pre-Honeycomb Android, and I have not been able to find a good workaround.

Bug 808666 is on Jelly Bean, but I cannot reproduce it.

Comment 8

[(inactive) Jim Chen [:jchen] [:darchons]]

Pretty sure now that it's a bug in pre-Honeycomb Android, and I hadn't been able to find a workaround. Lowering priority unless it becomes more of a problem.