Post #714663
2026-03-15 14:41 UTC
Replies (7)
-
@village604@adultswim.fan 2026-03-15 14:59
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.
-
@Dave@lemmy.nz 2026-03-16 00:39
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.
-
@new_world_odor@lemmy.world 2026-03-15 16:32
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.
-
@scarabic@lemmy.world 2026-03-15 19:13
The iOS browser has always supported “tap the top of the viewport to scroll all the way up,” which largely allows for what you say: just leave the nav way up there. Last time I looked was years ago, and Android Chrome didn’t did this. Does it now?
-
@MonkderVierte@lemmy.zip 2026-03-15 16:53
I have this usercss: ``` [data-testid="header"], [data-mobile-fixed="1"], [data-remove-fixed="0"] { position: absolute !important; width: 100%; } main { padding-top: 2rem !important; } ``` Works well enough on most sites. And on those it doesn't, you can easily exclude. Can likely be expanded, but adding just `header` broke more than it fixed.
-
@MisterFrog@lemmy.world 2026-03-16 00:45
I like it at the top of the view-port, but I agree the auto-hiding/showing feature is excruciating.
-
@ulterno@programming.dev 2026-03-15 14:48
At the same time, it needs to be comfortably thin.