When i press a parent comment it hides all child comment but then parent comment also becomes hidden. Please change this behavior. Comments shouldn’t hide for a single press . When you long press the parent comment it should only hide all its child comments. Parent comment should still be visible.

  • joshLaserbeam@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I was about to post an enhancement about this and coming from Sync and Relay, I expect that tapping on a comment with child comments would hide just the child comments, while leaving the main comment fully expanded. And for comments without replies to have no change. But not all apps do it like this.

    It seams Jerboa follows the official reddit app in hiding comments, where all comments are hidable, regardless of replies. And the tapped (parent) comment is the one being hidden.

    I am not sure which behavior is better (I prefer the former, like you), maybe this should be a toggle? If the current system is the intended behavior, then a truncated bit of the comment should be in the hidden comment. i.e a comment saying “Lorem ipsum dolor sit amet, consectetur”, when hidden would read: User “Lorem ipsum…” 5 • 1h

    • lol@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      He shouldn’t follow that garbage official app. He shouldn’t try to copy/take inspiration from superior third party apps like sync, boost and Apollo.

      • joshLaserbeam@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Actually, Jerboa’s behavior matches closer to the apps, Alien Blue and Apollo, the way it collapses to a minimalistic 1 line with username and vote count. I hadn’t actually used Apollo, I don’t have an iphone, so I don’t know how it works. I’m only comparing it to things I had used (Sync, Relay). I would rather if Jerboa followed the behavior of Sync, Boost, and Relay. The important thing is we shouldn’t push towards or away certain design decisions, just because the official does does it. He should pick and choose features which benefit the user, regardless of where it comes from.

    • Excuse my ignorance, could you elaborate on what would be the benefit?
      I did file a request for being able to collapse all comments above the current one until it leaves the parent visible. But collapsing all below would be non-intuitive to me.

      • joshLaserbeam@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Let me show you with pictures when tapping on a comment on each app:

        Relay: Expanded and collapsed

        Sync: Expanded and collapsed

        Official: Expanded and collapsed

        Jerboa: Expanded and collapsed

        See the way only the comments disappear on the 3rd parties with an indicator on the side to show comments are hidden? And on the official app the comment goes to a small gray preview of the comment? The way Jerboa works now is closer to the Official reddit app, but has no context of the comment, like the Official reddit app. I think it should either 1) change the behavior to be more like the other 2 I show, or 2) keep it as is, but add context to the collapsed comment.

        I would prefer option 1 because that is more intuitive to me, but I think that is because that is what I’m used to, and not because it is the “right” way of doing it.

        • I see what you mean. Jerboa leaves only the username visible but hides the comment from view. I just checked Boost which i used, and it does the same. I’m with you in that being able to find a specific sub-thread again after it has been collapsed would indeed be good. I would prefer the collapsed comment not to take too much space, so that would be small font and truncation for me.

          I found the collapse function somewhat unusable anyway, because i would want to collapse when i had reached the end of a branch in a sub-sub-thread, but then i’d want to collapse only that branch which i had just read, so that i could get back to the parent of that branch, get the context again, and start reading the next branch from there. Therefore i’d find a collapse-up function logical. It could still leave a bit of context of already-read stuff visible, though, as long as it doesn’t take too much space.

          Care to file a feature request over at github?
          Just found that this might already be done in the next version: https://github.com/dessalines/jerboa/pull/438

  • kevin@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I 100% agree with you, we’ve implemented this as an option and it’ll be in the next release.