this post was submitted on 12 Oct 2023
17 points (94.7% liked)

Jerboa

10135 readers
1 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
[email protected]
17
Comment Navigation (lemm.ee)
submitted 1 year ago by [email protected] to c/[email protected]
14 comments fedilink hide all child comments
 

I used Joey for years for Reddit and it has an incredibly useful navigation feature that would allow you to use arrows to jump through every top level comment.

This app would benefit so much from this feature.

Trying to upload an image but receive an error.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

And yet it only happens with Jerboa and not other apps that the AOSP keyboard types in.

I'd read that it was to do with the specific rich text editor that Jerboa uses, and that it was a known problem with anything that uses that RTE.

[–] [email protected] 6 points 1 year ago (1 children)

Jerboa uses Jetpack Compose as toolkit instead traditional Views system that most apps use. The problem lays at core of a textfield component. It affects every app that uses this toolkit. And we can't fix because it would need to be fixed at very low level, we don't have access to nor domain knowledge about.

[–] [email protected] 2 points 1 year ago (1 children)

So, am I right that it's basically Google devs' bug to fix?

[–] [email protected] 3 points 1 year ago (1 children)
[–] [email protected] 2 points 1 year ago (1 children)

Thanks for the link. Looks like the bug was only first discovered in July, issue logged in August, so it's not been that long yet really.

[–] [email protected] 3 points 1 year ago (1 children)

Discovered in July 2022, I joined in July 2023 where I then pushed the issue upstream