The issue is that I can already scroll to the top to see the navbar, and interacting with it is a small fraction of what I do on a website. In fact, when clicking into media (like a news article or blog post), I'm not even going to interact with it once.
Yet I must endure all of its downsides the whole time I'm on the page, from taking up precious screen real estate to the even more annoying approach of popping in and out when I scroll up/down one pixel.
Just think of how seldom you interact with the navbar of most webpages and why it then needs to follow you around the page in the off chance that it's more convenient than just scrolling to the top.
So far I remain unconvinced that it can be done well since the entire premise is flawed: my device already gives me a one-click scroll-to-top shortcut. Like inertia scrolling, it's a bad smell when every website thinks it has to bring its own implementation of feature devices should already have.
Yet I must endure all of its downsides the whole time I'm on the page, from taking up precious screen real estate to the even more annoying approach of popping in and out when I scroll up/down one pixel.
Just think of how seldom you interact with the navbar of most webpages and why it then needs to follow you around the page in the off chance that it's more convenient than just scrolling to the top.
So far I remain unconvinced that it can be done well since the entire premise is flawed: my device already gives me a one-click scroll-to-top shortcut. Like inertia scrolling, it's a bad smell when every website thinks it has to bring its own implementation of feature devices should already have.