Composing range breaks key input on Android

[LucasAschenbach]

The TextInputClient behaves differently with respect to how it sets the composing range on different platforms. Unlike other platforms, Android always sets the composing range around the entire current word. Since CustomTextInput won't send key input events to the terminal backend unless the composing range is collapsed, this prevents sending modifier key combinations, autocompletion, etc. on Android.

I'm not really sure how to approach this since respecting the composing range is needed for supporting CJK. Perhaps there is an API for checking whether the keyboard is composing CJK.

[LucasAschenbach]

I just tested the text input with a Chinese keyboard on Android and it worked fine without the composing range. Apparently, Android has a separate composing buffer for Chinese keyboards (iOS doesn't, and I would imagine as do some other platforms). Ignoring the composing range on Android devices would solve the problem. However, it's not a very nice solution IMO.

[LucasAschenbach]

For anyone encountering this issue: Setting the obscureText property in the TextInputConfiguration to true should serve as an easy temporary fix. However, this fix merely disables text composition and therefore loses support for CJK.