• bleistift2@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    ·
    15 days ago

    Unless the user is actively navigating, the header is dead weight. The header should hide on scrollDown and reveal on scrollUp. Let the content breathe.

    This one I actually hate. Often I just want to scroll up a few pixels, either to satisfy a mild compulsion or to align the content so I can see most of it. This is completely ruined if the navbar pops back in. Leave it at the top of the page, where it belongs, not at the top of the viewport!

    • new_world_odor@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      15 days ago

      I feel your pain. The really good ones plan for this, some pop up immediately when you scroll up and that sucks. The proper thing to do (imo) is to wait for the user to scroll 80% of the viewport back up, only then letting it begin to slide in, and have it slide in at a rate 1/2 of the page scroll. I do like having it easily available, but it should feel like it’s trying to stay out of the way.

    • Dave@lemmy.nz
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      14 days ago

      IMO the header should stay at the top as part of the page. I know where it is, I’ll scroll up to it if I need to.

      Like you, I find a header appearing and hiding quite difficult in specific circumstances.

      • acosmichippo@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 days ago

        100%. i like using the top of the screen to mark my place in reading. sometimes i need to scroll back up and these headers completely fuck up my reading experience.

        but luckily Reader View exists, so i usually just use that.