Closed Bug 56134 Opened 25 years ago Closed 25 years ago

frameset causes wrong "last page visited" to be loaded in new browser

Categories

(Core Graveyard :: History: Global, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 58613
mozilla1.0

People

(Reporter: barrowma, Assigned: alecf)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/4.7 [en] (X11; U; SunOS 5.6 sun4u) BuildID: 2000092908 When the browser is configured to load the "last page visited", and the last page visited is a frameset, only one of the frames, and not the whole frameset, is loaded when a new browser window is created. Reproducible: Always Steps to Reproduce: 1. Set Navigator to display the last page visited ("When Navigator starts up, display..." under Navigator preferences) 2. Visit http://developer.netscape.com/docs/manuals/index.html (or any other frameset) 3. Spawn a new Navigator window (CTRL-N) *OR* exit the application and start it again. The content of the new window will be only the content of one of the frames of the frameset page you last visited, not the whole frameset. Actual Results: The content of the new window will be only the content of one of the frames of the frameset page you last visited, not the whole frameset. Expected Results: The new browser window should display the whole frameset of the last visited page.
this is a duplicate report. I will try to find the original.
Component: Browser-General → History
The original bug for creating the ability to do "last page visted" is bug 32269.
reassign.
Assignee: asa → radha
QA Contact: doronr → claudius
Confirmed with 110204 mozilla trunk win32 build on NT4
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 59387
This is global history problem, the way urls are added to global history in docshell. giving to rjc
Assignee: radha → rjc
I meant bug 36269 (oh so long ago)
taking this. Sounds like we need to somehow distinguish between the last frameset visited and the last page visited? :(
Assignee: rjc → alecf
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
nav triage team: not a beta stopper.
Keywords: nsbeta1-
Component: History: Session → History: Global
Marking nsbeta1+ because I think we should fix this. Leaving mozilla1.0 because I don't know where to schedule this right now.
Keywords: nsbeta1-nsbeta1+
Marking this as a dup of 58613 because that bug has more useful info in it (well, a comment by Radha what the problem is) *** This bug has been marked as a duplicate of 58613 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
VERIFIED Dupe
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.