this post was submitted on 08 Aug 2023
38 points (93.2% liked)

Jerboa

10300 readers
19 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
dessalines@lemmy.ml
38
Bug report: Backspace behavior when writing comments (lemmy.world)
submitted 1 year ago by bonnetbee@lemmy.world to c/jerboa@lemmy.ml
18 comments fedilink hide all child comments
 

Does anyone else have this weird backspace behavior when writing comments? I would describe it like this:

When writing a comment or a post I sometimes press backspace a few times to correct a word. This will delete a few characters and then delete the space between the current word and the word before this word, resulting in: first wordsecon

Can anyone describe this in a more technical way? Is this already an issue on github? I couldn't find it last time I looked.

you are viewing a single comment's thread
view the rest of the comments
[–] theshatterstone54@feddit.uk 15 points 1 year ago (3 children)

It is one of the oldest issues on GitHub. I assume you're using either AOSP Keyboard or OpenBoard, beacsue so far it seems that it only happens on those keyboards. I don't know about AOSP Keyboard, but with Openboard, in the Text Corrections section, if you disable "Show correction suggestions" it should work properly now. Link to issue: https://github.com/dessalines/jerboa/issues/194 There is a comment there from the user MV-GH who has posted a screenshot (it's near the bottom) of the option you need to toggle off and it will work properly. If you need correction suggestions, I'd recoomend either switching the keyboard or switching the client.

[–] FlappyBubble@lemmy.ml 4 points 1 year ago (1 children)

I use GrapheneOS with stock keyboard and the issue is there. It really shouldn't be up to the end user to change the keyboard though and the fix you describe doesn't work unfortunately. It should be fixed on Jerboa. It doesn't happen in other apps.

[–] theshatterstone54@feddit.uk 3 points 1 year ago* (last edited 1 year ago) (1 children)

Really? Worked for everyone else? Also, I totally agree, but the dev doesn't seem to have done anything. Edit: the issue arises from The keyboard, not from the app itself

[–] FlappyBubble@lemmy.ml 3 points 1 year ago

Very strange. Works on my other phone running Samsung's flavor of Android.not on my GrapheneOS though.

[–] Hopscotch@lemmy.ml 3 points 1 year ago (1 children)

Thanks for posting the GitHub link.

[–] theshatterstone54@feddit.uk 1 points 1 year ago

You're welcome!

[–] bonnetbee@lemmy.world 2 points 1 year ago (1 children)

Thank you, that was exactly it. Using AOSP Keyboard with text correction. And thanks for the github link!