I see that Compose WASM on an Android Chrome brows...

# compose-web

[Rok Oblak]

I see that Compose WASM on an Android Chrome browser has completely broken text fields, on my app and others, for example:

https://kdroidfilter.github.io/ComposeMediaPlayer/sample/

It may be just my device/keyboard (Samsung Keyboard, everything default as far as I am aware) but I wonder if anyone else on an Android browser can reproduce?

[bod]

Seems to work on my side

[bod]

woops sorry this is Firefox actually 🤦 . I forgot I switched.

[bod]

But also works in Chrome

[Seri]

Looks fine on a Pixel 2 / Chrome

[Rok Oblak]

Thanks both. I should clarify, by broken text fields, I mean when typing, it seems to sometimes just replace the last character, sometimes insert a selection from history (?), sometimes inserts two characters, etc.

[Winson Chiu]

That can happen if your onTextChange state update isn't immediate, causing multiple writes to conflict, although I'm not sure it explains all of those symptoms.

[Rok Oblak]

in my app, it only happens (and very consistently, in all text fields) on this Android browser, on mac browser and other platforms it all works fine

[bod]

on my side: on Chrome the completions are not working, on Firefox they are. (I'm using SwiftKey keyboard)

[bod]

typing characters otherwise work for both

[Ghasem Shirdel]

https://youtrack.jetbrains.com/issue/CMP-7298/Keyboard-Not-Opening-and-Page-Shifting-on-Focus-in-Compose-Web-App-within-Android-WebView

https://youtrack.jetbrains.com/issue/CMP-6816/Incorrect-TextField-behavior-on-mobile-browsers

[PHondogo]

T9?

[PHondogo]

Soft keyboard integration for web is not implemented correctly yet. There is an issue for that posted previously in this thread (CMP-6816)

[Stefano Milani]

@Rok Oblak for is fine on Pixel7 in Chrome and in DuckDuckGo