1571266 - Umlaut and accented characters do not generate keypress event

Status: RESOLVED INCOMPLETE

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

Description

[Thomas A]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

1. Go to https://www.quirksmode.org/dom/events/tests/keys.html
2. Select the input box in the middle of the page
3. Write "ä" (tried with Swiftkey and Samsung keyboard)

Note: I just noticed that Android Chrome does not produce the keypress event for any key. However my Firefox desktop browser generates keypress for normal ("a") and accented keys ("ä").

Actual results:

Test Results log says:
keydown on text
keydown on form
keydown on #document
keydown on window
keyup on text
keyup on form
keyup on #document
keyup on window

Expected results:

Test Results log shows (keypress is now shown):
keydown on text
keydown on form
keydown on #document
keydown on window
keypress on text
keypress on form
keypress on #document
keypress on window
keyup on text
keyup on form
keyup on #document
keyup on window

Comment 1

[Thomas A]

I checked out the events in WebIDE/Console and got this:

Android:

window.onkeypress=console.log; window.onkeydown=console.log; window.onkeyup=console.log;

# Write "aä" in the input field

keydown { target: input#testInputMinimal, key: "a", charCode: 0, keyCode: 65 }
keypress { target: input#testInputMinimal, key: "a", charCode: 97, keyCode: 0 }
keyup { target: input#testInputMinimal, key: "a", charCode: 0, keyCode: 65 }

keydown { target: input#testInputMinimal, key: "Process", charCode: 0, keyCode: 229 }
keyup { target: input#testInputMinimal, key: "Process", charCode: 0, keyCode: 229 }

Windows:

window.onkeypress=console.log; window.onkeydown=console.log; window.onkeyup=console.log;

# Write "aä" in the input field

keydown { target: input#testInputMinimal, key: "a", charCode: 0, keyCode: 65 }
keypress { target: input#testInputMinimal, key: "a", charCode: 97, keyCode: 0 }
keyup { target: input#testInputMinimal, key: "a", charCode: 0, keyCode: 65 }

keydown { target: input#testInputMinimal, key: "ä", charCode: 0, keyCode: 222 }
keypress { target: input#testInputMinimal, key: "ä", charCode: 228, keyCode: 0 }
keyup { target: input#testInputMinimal, key: "ä", charCode: 0, keyCode: 222 }

Comment 2

[Thomas A]

Also tested with the Samsung keyboard with predictions turned off. The result is the same.

Comment 3

[Diana Rus]

Hi, I reproduce the issue with Samsung Galaxy S8+(Android 8.0.0) on builds Firefox Release 68.0, Firefox Beta 68.1b5 build 1 and Firefox Nightly 70.0a1 (2019-08-07).
Note: I have also tested on a different device Sony Xperia Z5 (Android 7.0) on Firefox Beta 68.1b5 and with other characters as well and the keypress event is not taken into consideration.
I think that this bug may be related to Bug 695626. Based on my investigation I will mark this bug as new.

Comment 4

[Makoto Kato [:m_kato]]

Process key may be valid if using software keyboard. It depends on software keyboard implementation, and it sometimes generate composing string instead of direct input string.

Comment 5

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.