This has been driving me nuts for a while. I’ll scroll past 50-100 posts and then realize I wanted to see a post I JUST scrolled past. So I swipe down to get back to it. But the app interprets this as “please refresh my feed”. So I’m sent back to the top. Having all of the items I just scrolled past now marked as read.

I could gamble and hit “hide all read posts” but I’m not sure if the app decided to mark the last post I wanted to see as read or not.

Android 1.11.3

  • Nemeski@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Are you using it on Firefox?

    This might help:

    html {
    	overscroll-behavior-y: contain;
    }
    

    You can try it with this uBO filter for example: vger.app##html:style(overscroll-behavior-y: contain !important;)

    • bogo@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      No, I’m using the Android app from the Play Store. I used to use the PWA from Chrome. I tried the PWA from Firefox but noticed some weird behavior.

      • Nemeski@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Hmm, then I have no idea.

        @[email protected] Would it still be possible to try adding that to the CSS? Pull to refresh implementation is still buggy on Android Firefox and this seems to help prevent it from using the browser’s own and using the app’s own instead.

          • Nemeski@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            If it is installed as PWA and you apply it to html I noticed that buttons in bottom bar seems to become unresponsive sometimes for some reason if I click on link that takes you to another site and then come back

            If I apply it to [data-test-id="virtuoso-scroller"] instead it seems to work better? Not sure where would be the best place for it.

            Edit: Nevermind, I now got that unresponsivenes thing even without any changes, so seems like it might be seperate bug.