this post was submitted on 16 Jul 2026
5 points (100.0% liked)

Thunder App

4203 readers
5 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 3 years ago
MODERATORS
 

Pretty much any interaction with the comment box creates highlights between two words. No matter how you tap, it's nearly impossible to just have one single cursor. Sometimes it'll shrink to a single space, but that's about it, and it's been like this quite a while.

Typing this post, I'm able to just tap and move the cursor, but if this were a comment, it would create a highlight between where it is, and where I tapped next, every time.

you are viewing a single comment's thread
view the rest of the comments
[–] darklightxi@lemmy.world 1 points 3 weeks ago (2 children)

Hey there! What Thunder version are you currently running? This issue should be fixed with the latest nightly build

[–] RampantParanoia2365@lemmy.world 1 points 3 weeks ago* (last edited 3 weeks ago)

It is v0.8.6, which I just installed yesterday. It hasn't been happening since then, though. I don't remember if I had experimental features on.

[–] RampantParanoia2365@lemmy.world 1 points 3 weeks ago (1 children)

Okay, nevermind, the behavior is still present (tho ironically, not for this comment) Are you reccomending the experimental features be set?

[–] darklightxi@lemmy.world 1 points 2 weeks ago

Hey! This issue is only fixed in the pre-release versions at the moment (v0.9.0-4). If you don't want to switch to a pre-release version, I'm hoping to get v0.9.0 out within the next couple of weeks which should contain the fix as well.