1811657 - no keyboard input after using the browser for some time

Status: NEW

(GeckoView :: IME, defect, P5)

Description

[Kevin Brosnan [Ex-Mozilla]]

From github: https://github.com/mozilla-mobile/fenix/issues/28545.

OS version: Lineage OS 20
Phone: OnePlus 9 Pro
FF version: 108.2.0
Keyboard: AOSP provided by LineageOS

I recently upgraded from LineageOS 19.1 to LineageOS 20, which seems to have started my problems with Firefox. After a while of using the browser, text input is not processed anymore by the browser. Special keys such as backspace, enter, etc. seem to work but everything else seems to be ignored. I looked into the ADB logs but did not find anything problematic. There seems to be some warnings and errors but nothing particularly pointing to an input error.

A quick fix for now seems to be closing the app and re-open it but this is rather problematic with private sessions, as this closes all the private windows.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[raphael.kiefmann]

Is there any update on this bug? I tried to do some debugging on my own but neither Android nor the app itself show any log messages I would consider relevant.

I noticed a few things with this bug:

• Firefox Focus does not have this bug
• the address bar always takes input from the keyboard
  • only the rendered content does not react to input
• using software, such as scrcpy that copies the display content and allows to use a computer's keyboard does not allow to input either
• sometimes the keyboard has a slight delay when trying to be opened when no input can be made
  • this only affects the rendered content once again

Comment 3

[raphael.kiefmann]

If you could give me any pointers I would be glad to help debugging this problem but as of now I cannot seem to find anything helpful.

Comment 4

[Rockie]

[spam redacted - mhoye]

Comment 5

[raphael.kiefmann]

The issue can be closed. After updating my device a few weeks ago it suddenly worked perfectly again.