6 ms·
> When I scroll to the top, I can see the top. Instead, when you begin to scroll to the top you can see the top. If you have an iphone, it's navbar behavior is
by sehr 12y ago
> When I scroll to the top, I can see the top.
Instead, when you begin to scroll to the top you can see the top. If you have an iphone, it's navbar behavior is identical to this.
http://usabilitypost.com/2014/05/24/the-scroll-up-bar/ http://usabilitypost.com/2014/05/24/the-scroll-up-bar/
- hnriot 12y agoon the iPhone you can just double tap the top of the screen to scroll to the top quickly.
- eropple 12y agoAnd when I want to resume reading? What then? Let's not be obtuse, yeah?
- ajanuary 12y agoWhat then? You tap the bottom of the screen to bring up the chrome instead.
- eropple 12y agoThere's no snapback to where you were reading if you double-tap the top. Which sucks and makes for a bad UX if you only need the top bar for a moment (for a share button, for example).
- ajanuary 12y agoI said tap the _bottom_ of the screen, not the top.
- eropple 12y agoAnd I'm pretty sure you lost the plot, because this thread is about the header library in the OP, not the browser chrome. Your suggestion to double-tap to the top (with a menu that doesn't follow you) means I lose my place. And so it's not a good suggestion.
- ajanuary 12y agoThe context of this sub-thread is on the iPhone you can just double tap the top of the screen to scroll to the top quickly. Which is all about browser chrome.
- eropple 12y agoDude. The iPhone was a comparison, not a concrete part of the discussion. Did you, like, read the posts before it in this subthread that are whining about how this thing is useless because you can "just" scroll to the top of the page to see the menu bar on the page? And, now, how tapping to the top isn't a good solution? There are enough upvotes on my posts here that I don't think this is that unclear.