Open Bug 706792 Opened 13 years ago Updated 2 years ago

Firefox "remembers" scrollbar position of non-"Things that scroll natively" elements after page refresh

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
8 Branch
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: azazel.private, Unassigned)

Details

User Agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.6.8; U; ru) Presto/2.9.168 Version/11.52

Steps to reproduce:

1. Open page http://fiddle.jshell.net/krkw7/5/show/ (there is scrolable div with some content)
2. Scroll div somewhere
3. Refresh page somehow


Actual results:

Scroll position restores. If its not -- do 2-3 a few times


Expected results:

Scroll position of non-"Things that scroll natively" like a div element should reset to 0
I've got the same Problem with Firefox 24 on Windows 7.
I've got the same Problem with Firefox 26.0 beta on Windows 7 x64.
Yeah, this is causing me grief too.
I should add, I'm on Firefox 27.0.1...
Also a victim of this same issue. None of the other browsers behave this way, and it's causing me and my team to spend time dealing with code workarounds that would otherwise work on elements that are removed and restored from DOM.

FF v 31.0
Still happening on Firefox 32. What is the recommended workaround? I've added:  `$("html, body").scrollTop(0);` after adding the dynamic content to the page, but even that gets overridden.

Ah, this one does appear to get the job done:

    setTimeout(function(){$("html, body").scrollTop(0);},10);
I am experiencing this on FF 33.0.2 using ExtJS 4.2.3. The scroll position of one of my infinite grids is not beginning at the top of the list, and so the list of records is not rendering properly. 

Firefox should not remember the scroll position of things such as overflowing divs. It should only ever remember the position of entire windows or frames.
This is still happening in FF 40.0.  I am using Dojo 1.10.4 and gridx 1.3.8.  When the page is refreshed, the grid stays scrolled to the position it was left in and causes issues with the paged data store. 

Please fix this asap, this has been open for nearly 4 years!
I'm using Firefox 41.0.2 and this was happenning for me only in Youtube -- quite annoying ... in order to keep the scroll position I had to open links in a new Tab! -- until now, but now it also happens with Google! These are for me (and for a lot of other people I suppose) the two most used sites!
Note that in IE9 both Google and Youtube behave as expected. Actually, IE9 behaves as expected!
So Firefox does not behave as expected. And I would bother to write about this in here, but is' the most annoying bug I have ever seen in a browser ... since I first used one in early '90s!

Please DO SOMETHING ABOUT THAT!  (I can't believe you are not able or unwilling to.)
Encounter the same issue while implementing an infinite scroll section, somebody please fix this 5 years old issue, thanks.
... After one and a half year: Does anyone from Mozilla read these comments/questions??? 
Not only these bugs remain unanswered but also unfixed!
What is the meaning or Firefox updating itself about every couple of months???
Well, I installed Firefox 55.0 and the problem of losing focus on Google pages is fixed!
We've got the the same problem with Firefox 61.0.1.
You can use this link https://dojo.telerik.com/azeViDOW/2 to reproduce the problem.

Is there an update is planned to solve the problem please?
Do you mean that the problem came back about a year after it has been fixed??? 
Also, https://dojo.telerik.com/azeViDOW/2 opens a *totally* blank page! Can't you give a workable link?
I have the same problem. It's reproducible and happens always.

Firefox 61.0.1 on Ubuntu 18.04 (Gnome based).
I'm running FF 60.1.0esr on Windows. The progrem of losing focus in Google and Youtube when using the Back button has been solved quite long ago ... (Are we always talking of this problem? :))
I'm running FF 60.1.0esr oo Windows. The problem of "losing focus in Google and Youtube when using the Back button is pressed" has been solved quite long ago ... (Are we always talking of this problem? :))
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.