When reading longposts I often lose my place by either a) accidentally tapping the Feeds button in the corner of the screen with the heel of my palm, which scrolls to the top, or b) accidentally tapping the article body (either while actively scrolling or just holding my phone), which collapses the post.

Anyone have advice for avoiding these on longposts? Skill issue?

  • Sjmarf@lemmy.ml
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    10 days ago

    a) accidentally tapping the Feeds button in the corner of the screen with the heel of my palm

    Apollo’s solution to this was to allow swiping left from the right edge to go “forward” to the page that was just closed. We’ve got an issue open for this feature here, but unfortunately this feature is rather tricky to implement so it’s unlikely to be added anytime soon.

    b) accidentally tapping the article body (either while actively scrolling or just holding my phone), which collapses the post.

    We’ll add a setting to disable collapsibility of post content in this week’s TestFlight (issue here) 👍

    • sqwOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 days ago

      For me I think I would still want the ability to collapse a post (via somewhat-rarely-used control/widget, under the hamburger etc) but disable the behavior of collapsing it when tapping inside it.

  • sqwOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 days ago

    i am definitely an enjoyer of the collapsibility of posts/post trees in the comment thread… but when its a longpost it just makes me lose my place while reading. maybe its just not a common-enough case to care that much… but longposts are often some premium stuff!