Closed Bug 44649 Opened 24 years ago Closed 24 years ago

Framesets with ambigious behaviour

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: pbotsas, Assigned: pollmann)

References

()

Details

Try on this site clicking on one of the categories in the left-handed 
navigation pane (like: History or Consulting).

The frameset opens correctly but then loads very strange. Instead of opening 
then content in the right frame it is opened in the parent window.

This site works in NN4.x and IE4+
The frames uses javascript routines like this one:

parent.content.location.href
I don't see a problem with this page - and also, I don't see that is uses 

parent.content.location.href=<url>;

See bug 33650, which was probably the real problem if that was what the links 
were doing.  Bug 33650 was fixed last week, so code above should work now as 
well.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
I tested the site (www.it-networks.com) with M16 Build 2000061311 which I 
downloaded on July 6th from mozilla-ftp.

Is there a newer Version???
Build 2000061311 should be 2000-06-13 11:00 or June 13th.  More recent builds 
are available here (but they are 'bleeding edge', so use at your own risk and 
all of the usual disclaimers):

http://ftp.mozilla.org/pub/mozilla/nightly/latest/

If I remember right, when I looked at this page, none of the links in the left 
frame used parent.content.location.href = ...  Are you still seeing the problem 
on this page?  If they are using parent.content.location.href = ..., I think the 
bug with referring to a frame named "content" was fixed after M16 and a more 
recent build from the above directory should fix the problem you are seeing!
I will give this a try ;)
Marking verified Works for me. Tested with Sept 19th build.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.