If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Autofocus attribute on text input breaks virtual keyboard input for number inputs

UNCONFIRMED
Unassigned

Status

()

Firefox for Android
Keyboards and IME
UNCONFIRMED
2 years ago
2 years ago

People

(Reporter: Dennis Meckel, Unassigned)

Tracking

38 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8622069 [details]
test-min.html

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150511103818

Steps to reproduce:

Device: Google Nexus 7 2013 with Android 5.1.1 and the default virtual keyboard.

Tested with Firefox 38.0.5 and Firefox Beta 39.0 from Google Play.

1) Open the attached file test-min.html
2) The "autofocused" text input will open the virtual keyboard
3) Tap on the number input field (default value: 123)
4) Tap again to position the cursor after the 3
5) Press the delete key on the virtual keyboard


Actual results:

Nothing but the tap sound of the virtual keyboard. The default value 123 of the number input field isn't deletable without closing and opening the virtual keyboard manually. It is also possible to add numbers, but 123 keeps indelible.


Expected results:

The number 3 should be removed from the number input field. Removing the autofocus attribute from the text input field solves the problem.
(Reporter)

Comment 1

2 years ago
This doesn't look like a clear Firefox bug anymore since I tested the problem with the following setups:

Nexus 7 2013, Android 5.1.1 with default Google Keyboard
Nexus 7 2013, Android 5.1.1 with SwiftKey
LG P880 4X HD, Android 4.4/CyanogenMod with Google Keyboard from Google Play
LG P880 4X HD, Android 4.4/CyanogenMod with SwiftKey

The problem gets confirmed by the setups with Google Keyboard. The setups with SwiftKey don't share the problem.

Google Chrome for Android doesn't have this problem with all mentioned setups.
You need to log in before you can comment on or make changes to this bug.