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!
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.
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!
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.
It really depends on the site for me.
What I really hate is a table that’s multiple scrolls long where the header row doesn’t follow.
At the same time, it needs to be comfortably thin.