Hahhh that would explain it! Now i know.
And do you have an idea why the backspace behaves like in the video (clearing existing blank spaces between words)?
https://nostr.build/av/efa7000874019e6f6989bddf92d7a8fabb6e85dd183f4a6da95cac6b5dcb7d4b.mp4
Discussion
This seems like the classic bug on GrapheneOS's default keyboard, which I believe is a very old version of GBoard.
You can see how the keyboard's auto-correction considers the space part of the word in this frame. This is an issue that happens on any app that uses the new Jetpack Compose UI elements. :(
Since this is so old, I am not sure when it will be fixed by the keyboard providers.
I've been suffering the same issue from the beginning but according to the associated github issue, it's the keyboard apps' fault for using the wrong APIs or something.
It's an incompatibility between the Keyboard implementation and Google's new UI framework Jetpack Compose. The two need to come together to solve this. There is nothing anyone else can do, besides changing the keyboard.
Yep, Open Board has the same issue. I believe AnySoft doesn't.
Feel free to add to the discussion here: https://github.com/vitorpamplona/amethyst/issues/154
Trying AnySoftKeyboard.
It seems better. Will see in the long run 🤞
If it's a big note, I just write it somewhere else and copy-paste.
Can't there be a compatibility layer workaround?
The app doesn't have a way to intercept these auto-corrections. The code is with the keyboard itself. :(
If you have a way to disable the auto-corrections on the keyboard settings and you don't mind doing so, then it works.
