on the iPhone you can just double tap the top of the screen to scroll to the top quickly.

And when I want to resume reading? What then?

Let's not be obtuse, yeah?

What then? You tap the bottom of the screen to bring up the chrome instead.

There'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).

I said tap the _bottom_ of the screen, not the top.

And 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.

The 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.

Dude. 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.