Reload loads wrong frameset




19 years ago
11 years ago


(Reporter: mozilla, Assigned: radha)


(Blocks: 1 bug)

Windows 2000
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)





19 years ago
This is a little tricky to do, but it is not going to be uncommon among users.

Steps to Reproduce:

1. Visit After page loads click on the top link in 
the left frame titled "FeatureCAM".

2. Let the new page load in the right frame. Now right-click in the right frame 
and select "Reload Frame".

3. Now click on the home button in the left frame (at the bottom). This will 
load the original page back into the right frame.

4. Press the reload button on the toolbar.

Actual Results:

The "FeatureCAM" link frame is loaded into the right frame.

Expected Result:

The "Home" page (the page specified by the frameset document) should be reloaded 
into the right frame.

Build ID: 2000090808

Comment 1

19 years ago
Using the back button to go back to the "Home" page makes it so that this 
doesn't happen. It seems that when clicking on the "Home Page" link, the URL is 
not put into history correctly.

Comment 2

19 years ago
Of course, this may be an issue of where history is being used when it 
shouldn't. I would think pressing reload on a framset would reload the pages 
specified by the frameset document regardless of the history. That's how it 
works in 4.x and it seems logical to me.

Comment 3

19 years ago
I could reproduse only after I shutted down Mozilla...


19 years ago
Blocks: 47238

Comment 4

19 years ago
I could reproduse only after I shutted down Mozilla...


Comment 5

19 years ago
Reloads wrong frameset?? The frameset is fine, but the frame src is the problem.
Target Milestone: --- → M19

Comment 6

19 years ago
Also, if the frameset page changes so that the src= locations for a frame is 
different, Mozilla won't honor the change when you click the reload button.  
This is noticable when decomposing frame bugs, but may happen in the real world 
as well.

A workaround for both problems is to click in the URL bar and hit enter instead 
of using reload.

Comment 7

19 years ago
But this workaround works only in the top frameset. If you have several
nested framesets, and an inner frameset page changes, you're (almost) lost.
I think the only way to make Mozilla really reload everything is to clear
the memory and disk cache. It works fine in Netscape 4.x.

Comment 8

19 years ago
Betting this is one of two bugs I looked at today:

Bug 53708: URLs load into wrong frames (new load wrongly detected as shist load)

This bug only happens on new loads of framesets.

Bug 52670: URLs load into wrong frames (shist stores frames at wrong offsets)

This bug only happens on session history loads of framesets with many frames, or 
where one frame towards the end of the list loads much faster (e.g. from cache) 
than the ones before it.

This sounds more like 52670, marking dup...
(fwiw, reload does force the last displayed frames to show, not the ones 
originally specified by the frameset)

*** This bug has been marked as a duplicate of 52670 ***
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE

Comment 9

19 years ago

Comment 10

18 years ago
The patch to bug 52670 does not fix this bug.
Resolution: DUPLICATE → ---

Comment 11

18 years ago
I also verified that the patch does not fix the problem. :S

Comment 12

18 years ago
It works for me on WinNT, build 2000101920. Is this OS specific?


18 years ago
Blocks: 59387

Comment 13

18 years ago
Bug 60554 seems related. I don't think the mis-loaded documents are restricted
to being within frames. If possible, you might want to check if the browser's
GET requests are going to the wrong server.
I've been getting everything from single images, to whole frames and even entire
pages being requested from the wrong server.
nav triage team: looked at this bug, it is not a beta stopper. bulk update of 
several such bugs. 
Keywords: nsbeta1-

Comment 15

18 years ago
Platform: PC
OS: Windows 98
Mozilla Build: 2001012205

marking as such.
Last Resolved: 19 years ago18 years ago
Resolution: --- → WORKSFORME

Comment 16

18 years ago
Marking VERIFIED wfm (6/8 build, win2k) -- I don't see any issues with the 
current framed page, but the page seems to have changed since the time of the 

Comment 17

17 years ago
Mass removing self from CC list.

Comment 18

17 years ago
Now I feel sumb because I have to add back. Sorry for the spam.


11 years ago
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
You need to log in before you can comment on or make changes to this bug.