It's already a feature
Bottom 2 arrows when in the comment section
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.
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.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
It's already a feature
Bottom 2 arrows when in the comment section
Oh, thanks, I needed an update!
I am on 0.48 and it's not there. And the 0.49 beta isn't showing this in the release notes at all.
Hey, I'm using 0.49 and to enable this feature, I think you must check the 'show parent comment navigation buttons' box, under the look and feel settings menu.
Thaaaaaanks! 🫶
RIF had the option to collapse all comments by default, so you'd only see the top comments and could expand them if you wanted to go down a thread. I really miss that feature.
I just wish they'd fix the text editor deleting the space before a word as you backspace from the end, merging words together.
Pretty sure they said that was a bug with the aosp keyboard
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.
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.
So, am I right that it's basically Google devs' bug to fix?
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.
Discovered in July 2022, I joined in July 2023 where I then pushed the issue upstream