This is my pet hate with Google's AMP mode which most sites seem to be switching to.
On my iPhone 5S it breaks hiding the browser's address bar when you scroll, then you have the AMP 'address bar' of the same size, then you finally get to the site's sticky header and footer. On Huffington Post the content is around 50% the size of my screen. Oh and it breaks Safari's Reader mode, which I assume also means accessibility features.
http://i.imgur.com/PNOQ4Hk.jpg
If anyone from Google is here, please do something about this as it is ridiculous.
And in case if someone from Google is listening, give the option to opt out of this AMP crap, I'll gladly pay for extra bandwidth.
While I understand the pain of (sometimes) having broken sites when AMP is on, this really helps when someone is on a country where mobile internet is expensive.
How exactly do you land on AMP pages? Can't you just use Firefox on you phone?
I believe this is actually due to Safari iframe bugs. See: https://medium.com/@dvoytenko/amp-ios-scrolling-and-position...
But that'd be crazy, right?
Since when?
On a regular desktop you would not have this problem: you can have a menu far away from the content. You can have tool bars. You have the name of the tab and the URL giving you context, and the page need less context switching because you can just display more instead of requiring to juggle with what the viewport can display. But on the mobile, context switching is very hard to do right, and must be accessible from your thumb.
It would also reduce the number of old articles submitted to HN as a nice side-effect.
Works already in Safari, but alas only in Chrome Beta.
It is a lot simpler and more robust than the Javascript approaches I found.
Note that what you want is different from what the user wants. I am not alone in thinking that stickies never add value, no matter how convenient the designer thinks they are: https://alisdair.mcdiarmid.org/kill-sticky-headers .
(It's always refreshing how civil disagreements on HN can be. Thank you for your thoughtful reply!)
So do we use a javascript solution that also performs like crap, or accept that this is a common use case and provide a standard way to do it?
Please install an ad blocker. uBlock Origin works wonderfully in Firefox for Android.
And let's keep in mind in the real world, it's going to be at least 3 times bigger than that because it's not a sticky bar for ants after all. And it'll be rocking its best friend Mr Hamburger Menu, some social-tracking-sharing-buttons, and a banner ad for whatever was mis-classified from the background of the weighted average of the last 10 Facebook pictures you appeared in.
Just the text please! Viva le reader mode!