this post was submitted on 17 Feb 2026
5 points (100.0% liked)

Voyager

8003 readers
18 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Download on App Store

Download on Play Store

Use as a Web App

Download on F-Droid

Rules

  1. Be nice.
  2. lemmy.world instance policy

Sponsor development! πŸ‘‡

Number of sponsors badge

πŸ’™

founded 2 years ago
MODERATORS
 

When I attempt to edit a comment that I already submitted, especially if I'm trying to backspace text, I put the text cursor at the desired part of my comment but if I backspace more than once (i.e. holding the backspace button), the cursor jumps to the very end and starts deleting the end of the comment.

Interestingly this very same glitch would happen to me on the reddit app when I used to use reddit.

Does anyone else get this on Voyager? Is it a known bug?

Edit: I suppose it would be helpful to add, I'm on Android.

top 9 comments
sorted by: hot top controversial new old
[–] QuadratureSurfer@piefed.social 1 points 1 hour ago (1 children)

I do not have this issue at all. I'm on Android using the Futo Keyboard.

Are you on Android or iOS? Are you using the stock keyboard app, or something else?

[–] Blackfeathr@lemmy.world 1 points 9 minutes ago

Android, using stock keyboard.

[–] Quetzalcutlass@lemmy.world 3 points 12 hours ago* (last edited 12 hours ago)

I'm running into this too. It happens when adding text to an existing comment, not just deleting, and only when editing multiple characters at once (swipe typing or holding backspace). It doesn't seem to happen when pressing a single button at a time.

The bug only happens once and seems to trigger the first time the number of lines changes and Voyager has to rewrap the input text, but it's not consistent (I've edited this comment about a dozen times now without it happening). And it never happens on a fresh comment, only when I go back and edit one later.

Running on Android with the HeliBoard keyboard.

[–] Jumbie@lemmy.zip 2 points 12 hours ago (1 children)

Your screen protector might be activating your touch screen. Eliminate that possibility first?

[–] Blackfeathr@lemmy.world 1 points 6 hours ago (1 children)

I don't have a screen protector.

[–] Jumbie@lemmy.zip 1 points 3 hours ago (1 children)

Then I dunno, man. Pretty sure it’s not the app. I’ve had phone screens act up like this in the past so I’m not just guessing.

Maybe you need a phone hard reset.

[–] Blackfeathr@lemmy.world 1 points 2 hours ago (1 children)

Another person in this topic is also having the same issue.

[–] Jumbie@lemmy.zip 3 points 2 hours ago (1 children)

Interesting. I tested for it in this comment with no issues.

[–] Blackfeathr@lemmy.world 1 points 9 minutes ago

That's odd. Are you on Android?