407447 - frame name not working

Status: RESOLVED INVALID

(Camino Graveyard :: General, defect)

Description

[Ray Woodbury]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: 1.5.4

If I code a top.framename e.g. top.botFrame.location.href = listValue; it ignores it but if I use parent.frames[1].location.href = listValue; this works. Is there something I have to set as I cannot change the whole web application and should not need to. Code works on Safari, Opera, IE

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Chris Lawson (gone)]

Does it work in Firefox 2.0.x?

Comment 2

[Stuart Morgan]

(In reply to comment #0)
> and should not need to.

Unless you are using an IE-specific, non-standard JS extension, which I suspect is the case here, and want the site to work in all browsers.

> Code works on Safari, Opera, IE

Opera tries to emulate IE behaviors as much as possible, and Safari is known to support some non-standard IE-specific JS, so that's not definitive. Can you find a DOM reference for that syntax?

Comment 3

[Ray Woodbury]

ok checked out and it seems that 'parent' is the DOM reference not top. The top started it seems from Netscape and copied by IE then copied by Opera, Safari etc.. Case closed. However, it would be good for Camino to support this as it is widely used and in so much reference material. In all my books and many online articles it's there. A small change in the scheme of things. many thanks

Regards Ray

Comment 4

[Chris Lawson (gone)]

INVALID because it's not a DOM call.

If you believe there's a good reason for Gecko to support this, please file a bug (probably in Core:DOM) asking for it.

Comment 5

[Ray Woodbury]

support of top a the parent reference. e.g. top.botFrame.location.href = listValue; as well as parent.botFrame.location.href = listValue;.

It would be good for Camino to support this as it is widely used and in so much reference material. In all my books and many online articles it's there. 

Comment 6

[Chris Lawson (gone)]

Yes, I get that. Please file a *new* bug in Core:DOM if you believe you have good arguments in favour of doing this. Camino developers have no control over the JavaScript engine in Gecko.

(Just to save you the trouble, "IE does it" and "It's in a lot of books" are not generally considered to be "good" arguments by the Gecko developers. "Here's a standard that says it should work this way" is a much stronger argument, but you're welcome to file the bug regardless.)