<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>iSnow</author><text>Good news is that the issue is recognized by the Mozilla team at the very least:&lt;p&gt;&amp;#62;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&lt;p&gt;&amp;#62;Status: 	RESOLVED FIXED&lt;p&gt;&lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=780345&quot; rel=&quot;nofollow&quot;&gt;https://bugzilla.mozilla.org/show_bug.cgi?id=780345&lt;/a&gt;</text><parent_chain><item><author>btilly</author><text>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.&lt;p&gt;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.</text></item><item><author>munificent</author><text>This seems to result in a large number of cases where the visual experience is pointless. The line separating the previous and next page is tiny and easy to miss, and I don&apos;t see the use in two torn half-pages on screen.&lt;p&gt;I agree that smooth scrolling long text is hard to read and trips up line scanning, but this UX seems be like playing an cruel game where I have to drag just enough to scroll a whole page. Any more or less and I get a torn page that&apos;s even harder to read than normal scrolling.&lt;p&gt;I have an alternate solution to this problem: &lt;i&gt;just hit space or page down&lt;/i&gt; when you&apos;re reading a long web page. It scrolls a whole page, with just enough animation to help you track where you are.</text></item></parent_chain></comment><story><title>I want the world to scroll this way</title><url>http://www.magicscroll.net/ScrollTheWeb.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>acabal</author><text>That&apos;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&apos;t usable.</text><parent_chain><item><author>btilly</author><text>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.&lt;p&gt;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.</text></item><item><author>munificent</author><text>This seems to result in a large number of cases where the visual experience is pointless. The line separating the previous and next page is tiny and easy to miss, and I don&apos;t see the use in two torn half-pages on screen.&lt;p&gt;I agree that smooth scrolling long text is hard to read and trips up line scanning, but this UX seems be like playing an cruel game where I have to drag just enough to scroll a whole page. Any more or less and I get a torn page that&apos;s even harder to read than normal scrolling.&lt;p&gt;I have an alternate solution to this problem: &lt;i&gt;just hit space or page down&lt;/i&gt; when you&apos;re reading a long web page. It scrolls a whole page, with just enough animation to help you track where you are.</text></item></parent_chain></comment><story><title>I want the world to scroll this way</title><url>http://www.magicscroll.net/ScrollTheWeb.html</url></story>