Closed Bug 59387 Opened 24 years ago Closed 5 years ago

[META] Frame history issues

Categories

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

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Status:
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.
Moving all contacts to me
Assignee: nobody → jerrybaker
QA Contact: claudius → jerrybaker
Depends on: 52001, 55517, 56134, 56625, 57402
Summary: [META] Frame navigation issues → [META] Frame history issues
Depends on: 29972, 31000, 31403, 32745, 36547, 41019, 45227, 46828, 50029, 50980, 52670, 53465, 55359
Depends on: 57403
No longer depends on: 57403
Depends on: 58216
Depends on: 54350
Depends on: 56062
No longer depends on: 56625
Adding meta keyword and changing Platform/OS to all/all.
Keywords: meta
OS: Windows 2000 → All
Hardware: PC → All
Keywords: mostfreq
Added self to CC.

nav triage team: not a beta stopper.
Keywords: nsbeta1-
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.
Depends on: 58906
Madness... We do not able to browse frames but it is nsbeta-... :(
Whiteboard: [dogfood]
Depends on: 66203
this bug also depends on bug 66564 and bug 69206
Depends on: 66564, 69206
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.


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.
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.
Depends on: 86330
Depends on: 83684
Depends on: 79063
Depends on: 90506
Depends on: 97074
No longer depends on: 97074
No longer depends on: 83684
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.
Does anyone know why bug 48422 is not listed as a dependency here as well?  It 
is an HTML Frames issue...isn't it?

I don't think it counts as a frame *history* issue.

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.
Mass removing self from CC list.
Now I feel sumb because I have to add back. Sorry for the spam.
adding bug 160869
Depends on: 160869
Depends on: 160933
Depends on: 162567
Depends on: 135700
Depends on: 156304
Depends on: 165779
Depends on: 166807
Depends on: 148805
Depends on: 118703, 162128
No longer depends on: 162567
Depends on: 178344
Depends on: 171165
Depends on: 207880
Depends on: 257498
Component: History: Session → Document Navigation
QA Contact: mozilla → docshell

15 years without any activity on this meta bug, closing.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.