That said, this solution will also break in that situation. But it will break worse since there will be no way to get the text at the top to scroll into view.
>Pages with position:fixed banners/headers are all the rage these days. But when I try to read content inside one of these pages and hit Page Down or Spacebar, firefox calculates the page length relative to the whole browser window, not just the part visible underneath the position:fixed header. So it scrolls too much, and the first few lines of the next page end up hidden
>Status: RESOLVED FIXED
Edit: Oops, I guess it's already there. I couldn't think of a site with an appropriately sized fixed header to test it, but Google+ is such a site and pagedown works perfectly there. Nice.
Works for me on FF17. Does not work on Safari or Chrome.
BusinessWeek.com articles don't totally work. They seem to have an extra pop with their header. So 2 levels of BS. Can't totally fault the browser there.
Techcrunch.com works perfectly fine too.
So yes, fixed in FF17 and also seen to work on FF18.
I often use the "page style: no style" in firefox setting in firefox in the view menu. That gets rid of fixed positions and a lot of other annoyances.
javascript:for(var a=document.querySelectorAll('*'),i=0,e; e=a[i]; i++) if (e.currentStyle.position == 'fixed') e.style.position = 'static'; void(0)
It works perfectly. Well, I vaguely recall there was one site, where it didn't work, don't remember which one (nor cared to figure out why it didn't). At first I was worried that looping over all elements on a page would be too inefficient, but JS is so fast nowadays, there's no noticeable delay. Also, there's no getElementsByStyle method, so I'm not sure how to even go about optimizing that loop.
So you're saying the working solution doesn't work on sites with completely broken UIs such as Google+? What a surprise.
That's like criticizing middle-click-to-open-in-new-tab because it doesn't work on broken sites implementing fake links via javascript, without actual links backing them.
You're saying the UI on Google+ is broken because the header stays on the top? I love that feature - more sites should implement it.
1. I'm saying the UI on Google+ is broken because the way it's implemented (and it's not the sole offender) means page-wise scrolling as described by OP does not work anymore.
2. But your suggestion that G+'s worthless header has no reason to stay fixed and eat up 20~30% of the vertical space is also correct.
Funny how frames are avoided for historical reasons when they often seem like the ideal solution. Remember when Twitter expanded conversations in a fixed box on the right of the screen? Should have used frames. Fixed header? Same deal.
Blogs wouldn't regularly collapse under load because blog posts could actually be static html pages instead of being dynamically generated just so we can slap the same header and linkroll on each one.
We wouldn't need new html5 tags to tell screen readers and crawlers where's the content and what's navigational elements because they would be in separate (i)frames.
Ajax's use could be actually reserved for interactive web applications instead of ugly optimizations like loading the comments separate from the article so the article itself loads faster.
I've been telling this to people for years, at my street corner, with my megaphone. But nobody is listening! It's a conspiracy!!!