1429316 - Keyboard not working properly in address bar

Status: RESOLVED INVALID

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

Description

[Krzysiek Grzembski]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171024165158

Steps to reproduce:

I have LG phone with android 6.0.1 (3.10.84) and in firefox have problem with keyboard. Everything works perfectly in other apps and in in firefox in other text-inputs different than address bar. For example: when using keyboard in google.com search input everything works. When using in address bar it is broken. Reinstalled app and nothing changed. 

My default system keyboard has in most bottom row layout like this:
[switch to symbols][kbd options][/][space][.][.com][GO]
where go acts like enter key. 


Actual results:

If i am pressing: 

[switch to symbols] then [switch to symbols] is pressed
[kbd options] then [kbd options] is pressed
[/] then [/] is pressed
[space] then [/] is pressed
[.] then [/] is pressed
[.com] then [space] is pressed
[GO] then [.] is pressed

it works like that only for last row. In other rows or other layouts (eg. after switching to [symbols] everything works and i can use [enter] without any problems.


Expected results:

Well, correct key should be pressed.

Comment 1

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

Jan, do you think this is a fallout from bug 1388112?

Comment 2

[Jan Henning [:JanH]]

What phone is it precisely?

Also, could you try this Nightly build (http://ftp.mozilla.org/pub/mobile/nightly/2017/08/2017-08-20-10-00-48-mozilla-central-android-api-15-old-id/en-US/fennec-57.0a1.en-US.android-arm.apk) and check whether this happens in that build as well?

Comment 3

[Krzysiek Grzembski]

LG Flex 2 (h955) european version (2gb/16gb)

Comment 4

[Jan Henning [:JanH]]

@Krzysiek
Can you also please install the Nightly build from the link above and see whether this behaviour happens there as well?

@jchen
I'd tend to say no, because the code to replace the user input only becomes active when an autocomplete result is available, which won't be the case when entering "/ ..com", but without being able to reproduce this, who knows...

Comment 5

[Krzysiek Grzembski]

It works now but i don't know why. There was no update for firefox but i have feeling that i have different browser. Aside of reported bug I had problem with firefox very slow connection stablishing. I took up to 15 seconds to open first site. Like some DNS problem. But now it is also gone. Everything work fast and smoothly.

Is it possible that some firefox files were changed without involving Google Play?