Is there a setting that might resolve the issue attached, where really long comment threads get squished into illegibility?

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    3 months ago

    Not off my head, no. Which is why I was asking if there were any other alternatives. I don’t particularly like that solution.

    Edit: Since I know the depth on a per-comment basis, maybe I could reverse it in CSS beyond a certain point and have them start going right to left? (spitballing here)

    • Coelacanth@feddit.nu
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 months ago

      How about this: as you scroll past an entire comment in the chain (the bottom of the comment leaves the top of the screen) the entire comment chain is shifted to the left?

    • over_clox@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 months ago

      We should start a ridiculously long comment thread here so people can see how the various Lemmy apps out there handle and render things…

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        3 months ago

        Lol, well, I’ll keep the ball rolling with this reply.

        It took me a while to notice this behavior (on any client) because once a comment thread gets that deep, it’s usually a slap fight I wouldn’t bother reading anyway lol

              • mryessir@lemmy.sdf.org
                link
                fedilink
                English
                arrow-up
                4
                ·
                3 months ago

                @!ptz@dubvee.org

                After stopping the scroll, animate to minus padding on the left (move tree to the left in its entirety).

                Or animate the margin between these comments to 0 until the end of the comments for the thread

                Or just stop at some percentage of screen estate and work with differing colors.

                Maybe you could use folds right above and below to indicate that the tree is rerooted?

                Spittballing back. Learned a word today!

                  • mryessir@lemmy.sdf.org
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    3 months ago

                    Nope. Way more hacky on the web.

                    On mobile it would be encapsulated and invoked on demand, easily supporting 300hz+ :).

                    At least I assume it; But I have my very limited experience on web development. Even if there would be an easy way due to javascript/browser compatibility it should be very cumberstone.

                    Though if we had a LISP-like language (Scheme) like initially intended we wouldn’t have to worry. Idk who to blame.

                    Someone wanted restrictions and this may have been a valid point.

                    I can’t judge but for mobile.