Thunder App

4152 readers

1 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 2 years ago

MODERATORS

darklightxi@lemmy.world

poolitzer@lemmy.world

darklightxi@lemmy.ca

micahmo@programming.dev

micahmo@lemmy.world

Editing comments has been near unusable since last update. (lemmy.world)

submitted 1 month ago by RampantParanoia2365@lemmy.world to c/thunder_app@lemmy.world

5 comments fedilink hide all child comments

The draggable cursor has been getting stuck on the span mode, and refuses to go back to the single cursor no matter where you tap. Sometimes the end even gets stuck at the end of the whole comment text, and can't be moved to span a single character, unless it's the last one. Sometimes it works fine, but usually not. It does usually seem to go back to normal if you cancel, and re-edit.

you are viewing a single comment's thread
view the rest of the comments

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

Hey there! Thanks for the report, are you using Gboard as your keyboard by any chance? If so, it might be somewhat related to a recent update with Gboard that's causing the underlying bug.

A workaround for this issue at the moment is to try tapping on the Shift key a couple of times which should get you out of the span mode temporarily. Or as others have suggested, using space to move the cursor around.

Unfortunately this issue is not directly caused by Thunder but rather the framework that Thunder is built on. See https://github.com/flutter/flutter/issues/184744 for more information. Once the upstream bug is fixed, I can push out a new update to fix the issue!