Toolbar buttons should scroll to top on second tap - eviltoast

For UI consistency, tapping the Feed button after you’re already in the Feed View should scroll to the top of the feed. That’s what similar apps do (like tapping the News button in Apple News).

If you’re worried about accidental taps, pressing it a second time should take you back to where you were in the feed.

The other toolbar buttons should work similarly. If you’re in the Inbox and you tap a comment, tapping Inbox should take you back to the main inbox. Tapping Inbox when you’re already in the inbox should scroll to the top of the Inbox (if you’re not there already).

  • Eric@lemmy.mlM
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    We’ve been working on it. A simple tap to jump to the top is pretty easy–things get tricky when you start adding complications like “jump back into the feed” or “navigate up a level,” which require a more sophisticated architecture from the ground up. It is in active development, though, so we hope to have a prototype out soon enough.

    • ahti@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      I’ve just had the quickest of glances through the code. Is the gesture for opening the user switcher the only reason for reimplementing the tab bar? It sound’s like you’re rebuilding a lot of functionality that you get for free (iirc) with the native tab bar.

  • Hauke@feddit.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I don’t remember who wrote this, but a while ago some team member stated in this sub they had ~merged a PR~ a PR in the works that implements the described behavior. Perhaps there are other issues that emerged from this?

    Edit: Clarification based on reply

    • SideshowBoz@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Yea! There’s a draft PR that I left sitting around waiting for some 0.19 lemmy changes and also because the feature was triggering some undesirable performance issues not related to the tab bar itself.

      Tbh it’s gotten faster just by building against iOS 17, I’m probably going to finish it up and merge it in since so many of us want this 🙈

      • Hauke@feddit.de
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        No worries, thanks for taking care of this and the explanation! :-) I certainly did not intend to complain in any way since I didn’t even have time to look into the GitHub PRs myself