Closed Bug 294454 Opened 19 years ago Closed 19 years ago

With bfcache enabled after Reload, Back and Forward Firefox doesn't return to the original position in the page

Categories

(Core :: DOM: Navigation, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ria.klaassen, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050516 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050516 Firefox/1.0+

With bfcache enabled after Reload, Back and Forward Firefox doesn't return to
the original position in the page

Reproducible: Always

Steps to Reproduce:
1. Go to a site, scroll down.
2. Click Reload, then click Back and Forward.


Actual Results:  
Firefox goes to the cached page but doesn't scroll down.

Expected Results:  
Firefox should scroll down.

Regressed between 4 May and 5 May (from the beginning of bfcache).
Assignee: darin → nobody
Component: Networking: Cache → History: Session
QA Contact: networking.cache → history.session
confirmed on windows 2000 SP4
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050516
Firefox/1.0+
Flags: blocking-aviary1.1?
Is this related to these?

Bugzilla Bug 216376
Bugzilla Bug 258133
Bugzilla Bug 293235
(In reply to comment #2)
> Is this related to these?
> 
> Bugzilla Bug 216376
> Bugzilla Bug 258133
> Bugzilla Bug 293235
> 
My bad, delete that last one.
WFM Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050602 Firefox/1.0+

tested it a few times.  works perfectly.
Reporter: Which site did you test on?
In reply to comment #5: on every site.
I tried 6 different sites, and the problem seems to be gone now.
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050614
Firefox/1.0+ ID:2005061409

->WFM
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Flags: blocking-aviary1.1?
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
You need to log in before you can comment on or make changes to this bug.