Closed Bug 315612 Opened 20 years ago Closed 15 years ago

Incorrect behavior when refreshing forums and other frequently updating pages

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: bsharitt, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051010 Firefox/1.0.7 (Ubuntu package 1.0.7) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051010 Firefox/1.0.7 (Ubuntu package 1.0.7) In serveral online forums(like Fark.com), when refreshing the page in IE or Safari, the browser keeps the current place, and you are free to continues scrolling down and read the conversation, and this is the type of beharior that is to be expected when you reload a page. Unfortunatly, when I do this in Firefox, it seems to keep it's position in relation to the bottom of the page, thus making the reader have to scroll back up and find the original position, before continuing reading. If anything, it would be nice to have some sort of option that allows you to specify keeping the position in relation to the top of the page instead of the bottom. Reproducible: Always Steps to Reproduce: 1. Go to a site with forums, like Fark.com, and enter on of the disscusions. 2. Scroll near the bottom of the page so that the last couple comments are visible, and the begining of comments box. 3.Wait a moment(like how long it may take to read the comments) and then refresh the page (Note: the actual position in page noted above is just to make it easier to see what is going on with an easy point of referance after the refresh) Actual Results: Assuming new comments were added, ffter the refresh, the previous comments I was viewing are now "above" my browser window, thus cause me to have to scroll up to find them again. Expected Results: I should have found myself at the same comments I was at, thus able to continue scrolling down and continue reading.
Can you try this again with a trunk build of Firefox? I think this was fixed on trunk (but not on the branch for Firefox 1.5) in bug 278739.
It does work as expected in trunk builds.
WFM per previous Comment.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.