4 ms·
Your alternate solution gets annoying if the page has a header overlaying the text. Like Google+ does. Then you scroll a page, and have to scroll back a littl
by btilly 14y ago
Your alternate solution gets annoying if the page has a header overlaying the text. Like Google+ does. Then you scroll a page, and have to scroll back a little.
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.
- masklinn 14y ago> Your alternate solution gets annoying if the page has a header overlaying the text. 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.
- nollidge 14y agoHow is that a broken UI? Should they use frames instead?
- icebraining 14y agoNo, they should allow the header to scroll with the rest of the page.
- usaphp 14y agoIt's not a broken UI of Google, it's a browser related issue, wrong calculations of page height.
- btilly 14y agoPage height is calculated exactly the same way in all of the major browsers, and was calculated that way when Google+ created their interface. The fact that browsers are working around it to make a usability fix to benefit web designers does not mean that the fault does not belong to the web designers who intentionally built broken interfaces.
- nitrogen 14y agoIf they want a frame, they should've just used a <frameset>.
- myko 14y ago> So you're saying the working solution doesn't work on sites with completely broken UIs such as Google+? What a surprise. 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.
- masklinn 14y ago> You're saying the UI on Google+ is broken because the header stays on the top? 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.
- myko 14y agoUsing space to scroll on G+ works great for me. Even better, j & k - though I don't expect most people to use their keyboard at all to scroll.
- NoPiece 14y agoWhat browser are you using? Others have mentioned Firefox has updated to address the issue, but Chrome will scroll too far (full window height) when you hit space, which makes using G+ on other fixed header sites super annoying for us keyboard scrollers.
- repsilat 14y agoI guess the situation becomes "good enough" when all the modern browsers include a hack to make scrolling work properly, but it's certainly not ideal. If anyone ever decides to write another browser they'll have to deal with another undocumented requirement, and there are funny cases to consider like transparent fixed headers. 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.
- acabal 14y agoThat's why I utterly loath the stupid new trend of having fixed headers. They mess up my reading experience and honestly I thought we all ditched iframes a decade ago because even then we realized that putting frames everywhere isn't usable.
- Scaevolus 14y agoThey're especially annoying on devices with small vertical resolutions, like netbooks.
- augustl 14y agoI wish my browser had a setting called "disable scroll events and position: fixed"..
- itry 14y agoYou could write a bookmarklet for that. 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.
- yozmsn 14y agoFacebook probably looks awesome when you do that.
- tripzilch 14y agoI already did: javascript:for(var a=document.querySelectorAll('*'),i=0,e; e=a[i]; i++) if (e.currentStyle.position == 'fixed') e.style.position = 'static'; void(0) I nicknamed the bookmark "fix", so I can just type "fix" in the address bar to fix those pesky fixed elements. 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.
- aj700 14y agoI've noticed this problem with using the spacebar. But a top and bottom header will never add up to more than 1/3 of the vertical height of the browser window. Should be poss to build a javascript overlaid scroller button than only scrolls pages by 2/3 of window height at a time, in either direction?
- iSnow 14y agoGood news is that the issue is recognized by the Mozilla team at the very least: >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 https://bugzilla.mozilla.org/show_bug.cgi?id=780345 https://bugzilla.mozilla.org/show_bug.cgi?id=780345
- graue 14y agoThat's great news. Do you know what release this will land in? 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.
- shardling 14y agoIt says it landed in FF17, which I think should mean it's there already?
- hollerith 14y agoWhat about the bug where Edit > Find scrolls the page so that the hit is at the top of the window, but there's a fixed element hiding the hit?
- jyap 14y agoI just tested it on: http://www.raspberrypi.org/phpBB3/faq.php?sid=3eaf67c60d15ce99f041b9772e6a507f http://www.raspberrypi.org/phpBB3/faq.php?sid=3eaf67c60d15ce... 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.
- mikeash 14y agoIt's not the solution that's annoying here. Those overlying page headers that break space/pagedown need to die a horrible horrible death, and possibly their creators with them.
- monochromatic 14y agoGoogle+ sucks in pretty much every single way possible.