212168 - in javascript, i am unable to access the frames using parent.frame. .... which works fine in NS 4.77, NS 6

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Amit Gautam]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: 

top.frames["contentFrame"].document.frames[""]
top.frames.contentFrame.document.frames has no properties.
Using debug we found it gives an error that top.frames.contentFrame is not an 
object. this works perfect with NS 4.77, NS 6, IE 5 and above.



Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Phil Schwartau]

Rhino is a standalone language engine. This needs to be 
reassigned to the Browser product instead. 

Is there a URL we can go to, or a reduced testcase you can 
attach (via the "Create a New Attachment" link at the URL
for this bug)? Thanks, that will help -

Comment 2

[Boris Zbarsky [:bzbarsky]]

Please attach an HTML testcase showing the bug, using
http://bugzilla.mozilla.org/attachment.cgi?bugid=212168&action=enter -- the
information you have given is insufficient to determine the problem (as in,
top.frames works for me in all the testcases I've tried...)

Comment 3

[Fabian Guisset]

Arnit please attach a testcase in this bug, otherwise we will not be able to do
anything about this bug. Are you for example giving the name to the frame
dynamically? Does it look similar to bug 161061?

Comment 4

[Boris Zbarsky [:bzbarsky]]

No response from reporter, so marking worksforme.  Please reopen if there is a
testcase showing the bug.