26694 - iframe not reflected in top.frames until second iframe inserted via javascript

Status: VERIFIED FIXED

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

Description

[Myk Melez [:myk] [@mykmelez]]

Overview Description: 

An IFRAME in an HTML document should be reflected in the DOM after the IFRAME
tag has been parsed, but that isn't happening.  top.frames.frameName is
undefined after the IRAME tag, and top.frames.length is zero.  However, if I
subsequently insert a frame using the javascript DOM api, not only does my
second frame appear but my first one does too.

Steps to Reproduce: 

1) In an HTML document, define an IFRAME tag.
2) Access top.frames.frameName and top.frames.length
3) Create and add an IFRAME element to the DOM tree with document.createElement
and document.body.appendChild.
4) Access top.frames.frameName, top.frames.frameName2 and top.frames.length

Actual Results: 

After the first frame top.frames.frameName is undefined, and top.frames.length
is zero.  After the second frame top.frames.frameName and top.frames.frameName2
are objects of type Window, and top.frames.length is two.

Expected Results: 

After the first frame top.frames.frameName is an object of type Window, and
top.frames.length is one.  After the second frame top.frames.frameName and
top.frames.frameName2 are objects of type Window, and top.frames.length is two.

Build Date & Platform Bug Found: 

Linux 2000-02-04-08

Additional Builds and Platforms Tested On: 

none

Additional Information: 

I also tried to access the frame after the document finished loading in case
this affected things, but I get the same results.

Comment 1

[Myk Melez [:myk] [@mykmelez]]

Attachment: test case that pritns values of top.frames properties after creating frames

Comment 2

[Myk Melez [:myk] [@mykmelez]]

Attachment: test case

Comment 3

[vidur (gone)]

The problem was introduced fairly recently by a combination of the asynchronous 
reflow optimization and a checkin by me to not require content sink flushing on 
script evaluation. The frames list is one of the entry points we missed putting 
in explicit flushing calls.

Comment 4

[vidur (gone)]

Fixed on 2/11/2000. The recent asynchronous notification code in the sink and 
pres shell delayed creation of frames.

Comment 5

[Prashant Desale]

Verified with 2000-02-14-09.