[Terpfen]

Currently, it's not considered a bug per se, it's just how the Gecko engine keeps up with web pages that suddenly grow in size.

A few people are lobbying on Bugzilla to have this corrected, but it's not going anywhere yet, since the devs have bigger headaches than page positioning right now.

Of course, FF 1.5 will have 3200+ bugfixes: this might be among them.

[zeugma]

It really depends upon how you look at it, whether this is a "bug" or not. Where you end up on the page after a refresh is dependant upon the relative position you were at when you hit the refresh button. If you were at the bottom of the post at post 40, then after the refresh you are still at the bottom of the post, but unfortunately, are now at post 70. Lets say you refresh while at post 25 of a 50 post thread. At this point, you are scrolled about halfway down the page. When the page refreshes, there are 100 posts on the thread. Your position in the refreshed page will still be about halfway down, but this halfway point is now at post 50 rather than 25.

You might consider this behavior a bug, but there is really no way for Firefox to tell anything other than that it was halfway down before, and it is still halfway down after the refresh. The problem is the page is a lot longer now, so your position within the page seemed to have changed. The solution would be for there to be an option to have position be absolute as considered from the beginning of the page (i.e., keep my focus at the point that is 2000 bytes in) rather than a relative one as considered for the entire page. The way you prefer things to render is largely a matter of preference. Perhaps they'll make this an option in the future. I'd like it much of the time, though it could cause issues when rendering a page that has a lot of nested frames or tables.