Cursor goes back when typing bold text in mobile clients

[julien-nc]

In mobile clients, while having no text selected, if one selects Bold, Italic or Strikethrough and then starts typing, the cursor is moved back to the line beginning after typing the first character. So the first typed character is placed in the end.

If we type "Hello", we get "elloH" or even sometimes "HelloH".

This can be observed with Nextcloud Android client v3.18.1 with server master and Text master.

text.mp4

[julien-nc]

cc @juliushaertl @mejo- @max-nextcloud ^^

[julien-nc]

I tried with latest Text master (which includes the Tiptap 2 upgrade) and the issue is still there.

Maybe the issue is not about Tiptap but rather on the Android side (system or NC client).
In a virtual phone, I found out it works fine if you type text with the real physical keyboard. The issue is only there when one types with the virtual Android keyboard.

Out of topic:
Collateral issue found: If the NC instance uses a self-signed SSL cert and we accept to trust it in the Android client, it is impossible to open a txt/md file. We get this in the app's logs:

E/chromium: [ERROR:ssl_client_socket_impl.cc(980)] handshake failed; returned -1, SSL error code 1, net_error -202

So it seems trusting the cert has no effect on the embedded chromium used to browse Text.

[max-nextcloud]

@eneiluj could you try if this also happens on https://tiptap.dev ? That might give us a clue how nextcloud specific the issue is. If it also happens there we could also report it upstream.

[max-nextcloud]

Looks like this might be related to the focus on initial loading:
https://github.com/nextcloud/text/blob/stable22/src/components/EditorWrapper.vue#L423

It's somewhat surprising to me though that this also affects the current master as that does not have the focus(1, 1) anymore. So my intuition would be that it does not happen there anymore.

Anyway. Looks like for an empty document the state change does not happen initially and also not when hitting bold... but when the first letter is typed the state changes with state.initialLoading = true and this.initialLoading = false. So at that point the focus kicks in. (Just trying to come up with an explanation after noticing that removing the focus(1, 1) seems to fix the issue when debugging with @juliushaertl .

[juliusknorr]

After some further testing, this does not seem to be related to the autofocus focus(1, 1). When loading tiptap.dev inside the webview that is embedded within the android app, I can also reproduce the issue there.

However it seems to be only an issue when entering the text with the software keyboard on android, the issue is not reproduicable when typing on the actual keyboard through the chromium dev tools attached to the webview.

[juliusknorr]

Also found https://discuss.prosemirror.net/t/contenteditable-on-android-is-the-absolute-worst/3810

Issue is also reproducible with https://prosemirror.net/examples/basic/

[max-nextcloud]

I think we should report this upstream. I don't see how we could fix this ourselves without turning to very ugly hacks.

Maybe we could disable the buttons for marks (bold, italic, strike, underline) until there is some text on Android to avoid handing people a foodgun.

[juliusknorr]

@max-nextcloud I remember you worked mainly on this with the android team, was there any recent outcome ofter the revert of the user agent change on the android app?