Closed Bug 66203 Opened 24 years ago Closed 23 years ago

reloading a framed page creates multiple bad history entrys

Categories

(Core :: DOM: Navigation, defect, P3)

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 68847
Milestone:
mozilla1.0

People

(Reporter: MozillaUser, Assigned: radha)

References

(
URL
)

Details

Using build 2001012205. To reproduce, load any page with frames. Hit the reload button. Now, if you click on the back-button-drop-down-arrow thingy you will see the page's title repeated several times. None of these history entries work. If you select one, nothing will happen. If you just hit the "back" button, nothing will happen. If you select a history entry from BEFORE you got to the framed-page-where-you-reloaded you will go back just fine. This one is terure easy to reproduce, so I am quite surprised that I couldnt find it already in bugzilla... but if I DUP, the so be it. Bug 48501 and Bug 45227 both look as if they might be related, but not quite the same
Confirmed Platform: PC OS: Windows 98 Mozilla Build: 2001012205 Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 95 → All
win2000 moz2001011804
also Linux, 2001013010
Works just fine for me. QA, Please reopen if you can still reproduce it. Thanks.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
eepers! Re-tested with Build 2001021404 on Win95. The bug is still there. I can reproduce it on any-and-all framed websites I visit. This bug is the bane of my existance :P
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
definitely still reproducible w/ 2-14 builds. It looks like we add an entry for each frame in the page. This can be seen by looking at the popup associated w/the back button and by inspecting the 'Go' menu.
changing platform/os to all/all (cuz it happens on the mac too)
Hardware: PC → All
Status: REOPENED → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.0
check out bug 66564, it has the same symptoms as this one, and I just checked the javascript console and found that this bug is producing the a javascript error like that one is... *attempts to copy and paste error text* CURSES! You cant copy from the javascript console! If that aint already a bug, Im gonna go file it! *typing manually while grumbling* uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.goBack]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://navigator/content/navigator.js :: BrowserBack :: line 585" data:no] lets see...
adding frames-related meta bug 59387 to the block list.
Blocks: 59387
I think fixing bug 68847 last week fixed this bug too. I could reload just a frame or the whole page in the above site and I could not reproduce the problem. Can someone confirm that before I close this out? Thanks,
Yay! Spiffy spiffy! I just tested this on build 2001050104 on Windows 95 and it is happy! Marking this as a duplicate of bug 68847 Good work Radha! *** This bug has been marked as a duplicate of 68847 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 23 years ago
Resolution: --- → DUPLICATE
Verified on Linux 2001090608.
Status: RESOLVED → VERIFIED
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.