Closed
Bug 59387
Opened 24 years ago
Closed 6 years ago
[META] Frame history issues
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
Tracking
()
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
(Depends on 1 open bug)
Details
(Keywords: helpwanted, meta, Whiteboard: [dogfood])
This is a meta bug to track the confusing array of frame navigation issues in
Mozilla.
If anyone is getting spammed because of this bug, please feel free to do what
you must to stop it.
Assignee | ||
Comment 1•24 years ago
|
||
Moving all contacts to me
Assignee: nobody → jerrybaker
QA Contact: claudius → jerrybaker
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Comment 2•24 years ago
|
||
Adding meta keyword and changing Platform/OS to all/all.
Comment 3•24 years ago
|
||
Added self to CC.
Comment 5•24 years ago
|
||
Sorry for the spam, I just wanted to follow vishy's comment with a
clarification. nsbeta1- keyword means that Netscape management has decided that
it will not be able to contribute resources to fixing this for the next Netscape
release. It does not mean that a fix for this would not be accepted. Normal r=
and sr= checkin procedure still applies.
Comment 6•24 years ago
|
||
Madness... We do not able to browse frames but it is nsbeta-... :(
Whiteboard: [dogfood]
Updated•24 years ago
|
Keywords: helpwanted
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
adding cc: ...
Our web application is frame based and works well with NS 4.xx and IE 4.xx and
5.xx. It is useless with NS 6 because of the Back button problem. We exluded NS
6 from the list of supported browsers and discourage our clients from using it.
Yes, the Back button problem in frames is that bad.
Comment 10•24 years ago
|
||
Tal: Not that I would suggest that your clients use a pre-release browser, but
in fairness to Mozilla, have you tried 0.9? It could be that your problem is
already fixed (http://www.mozilla.org/releases/). Personally, I've found that
most frame-history issues work for me. Then again, you could be running into bug
56062 or bug 58906, both of which are still pending.
Comment 11•24 years ago
|
||
This is added just for the record since I already answered to Alex in a private
email message. http://www.mozilla.org/releases/ specifies explicitly that the
Mozilla releases should be used testing only so we cannot recommend them to our
customers.
couldn't this one be marked fixed? I havn't heard anybody having problems with
navigating frames for quite a while, and all depeing bugs are resolved.
Comment 13•23 years ago
|
||
Does anyone know why bug 48422 is not listed as a dependency here as well? It
is an HTML Frames issue...isn't it?
Comment 14•23 years ago
|
||
I don't think it counts as a frame *history* issue.
Comment 15•23 years ago
|
||
How about extending this meta bug for general frame specific issues (as opposed
to just history related) ?
We are doing extensive use of frames and having a centralized place to monitor
all frame related issues will be a great help.
Assignee | ||
Comment 16•23 years ago
|
||
Mass removing self from CC list.
Assignee | ||
Comment 17•23 years ago
|
||
Now I feel sumb because I have to add back. Sorry for the spam.
Updated•22 years ago
|
Component: History: Session → Document Navigation
QA Contact: mozilla → docshell
Comment 19•6 years ago
|
||
15 years without any activity on this meta bug, closing.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•