Closed
Bug 42865
Opened 25 years ago
Closed 25 years ago
some pages on securityfocus break future browsing
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
People
(Reporter: core, Assigned: radha)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m16) Gecko/20000613
BuildID: 2000061311
I went to http://www.securityfocus.com and it rendered correctly the first time,
but then I tried to navigate on the left menu to forums->bugtraq->archives and
the page came up without being in the framed environment. Then, the 'go' menu
no longer lists other www.securityfocus.com pages to navigate back to (you can't
back up to the previous pages). Then, if you type www.securityfocus.com back in
the url bar to go back to the beginning, the top frame doesn't render but
instead pops up a dialog box 'Unknown File Type' saying that the file is of type
'text/html, text/html'. The rest of the frames render.
Reproducible: Always
Steps to Reproduce:
1. go to www.securityfocus.com
2. click forums
3. click mailing lists
4. click bugtraq
5. click archives
6. try to back up to www.securityfocus.com and it won't work
7. Look at the 'go' menu to see that the previous pages aren't there
8. type www.securityfocus.com in the url line and hit enter to try to navigate
back to the main page and you should get the popup window.
Actual Results: see description
Expected Results: should have been able to back up to the main page, shouldn't
get a popup for the top frame (it works initially)
Comment 1•25 years ago
|
||
confirmed with 061611 win32 build under NT over to History.
Assignee: asa → radha
Status: UNCONFIRMED → NEW
Component: Browser-General → History
Ever confirmed: true
QA Contact: doronr → claudius
Assignee | ||
Comment 2•25 years ago
|
||
this is SH in frames problem
*** This bug has been marked as a duplicate of 36547 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
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.
Description
•