18
Comment Navigation (lemm.ee)
submitted 2 years ago by to c/jerboa@lemmy.ml
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.

all 15 comments

sorted by: hot top controversial new old
[–] 10 points 2 years ago (2 children)

It's already a feature

Bottom 2 arrows when in the comment section

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] 4 points 2 years ago

    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.

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 2 years ago (1 child)

    I just wish they'd fix the text editor deleting the space before a word as you backspace from the end, merging words together.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    Pretty sure they said that was a bug with the aosp keyboard

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 2 years ago (1 child)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •