bug(android): we should not be handling key events when the active input type is InputType.NULL
#13125
Open
1 of 8 tasks
InputType.NULL
#13125
Describe the bug
I initially found this issue when chasing down something else: #12848
When interacting with the main text input area on keymanweb.com, the active "input type" enum provided to us by Android is
InputType.NULL
: https://developer.android.com/reference/android/text/InputType#TYPE_NULLIn this mode, the keyboard has no view into any surrounding text. After all, the keystrokes should be directly interpreted, rather than editing text directly. After further examination...
Reproduce the bug
sil_euro_latin
(mostly working) andkhmer_angkor
(nothing working)Expected behavior
Our keyboard probably should essentially become passthrough for InputMode.NULL, simply passing keystroke event data through. Ideally, during that input mode, we'd avoid handling the physical keystrokes entirely, letting them be handled in a default manner. Alternatively, we could just forward everything through dispatchKey() to similar effect... I think.
Related issues
#12831
Keyman apps
Keyman version
18.0.183-alpha
Operating system
No response
Device
No response
Target application
No response
Browser
No response
Keyboard name
No response
Keyboard version
No response
Language name
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: