Moz/FF probs on displaying IFRAME (src only) inside invisible DIV

The Return of the NS-Reload Bug?

[hakre]

hi folks,

it came to my mind like a lightning that this might the rebirth of the old NS relaod bug and i really need feeback on this. test the following:

1.) create a div and make it invisble with javascript while loading the page (i.e. ele.style.display = 'none';)

2.) put an iframe into that div

3.) create a click event which toggles the div to be displayed (i.e. ele.style.display = 'block';)

the border of the IFRAME element will be correctly displayed but the content of the iframe is "nowhere".

tested with FF on win32, FF on macosx and MOZ on macoax (MOZ on win32 not tested).

i assume this is a rebirth of the so called "NS reload bug" but anyone who can point me in any direction, please let me know. because, toggle the visibility again and voila, content is there.

for anyone who want to check the life application <Sorry, no example links. See Forum Charter [webmasterworld.com]>

[edited by: tedster at 3:39 pm (utc) on Oct. 6, 2005]

[encyclo]

I'm seeing the same thing in Firefox 1.07 under Linux. It's a definite bug - I've poked around in Bugzilla but can't find anything corresponding to this exactly. It may be worth setting up a test page and submitting it.

We haven't seen the Netscape reload bug for a good long while now - it is certainly a similar bug but I doubt it is directly related to the original one. Does forcing a refresh with JS fix it?

[hakre]

We haven't seen the Netscape reload bug for a good long while now - it is certainly a similar bug but I doubt it is directly related to the original one. Does forcing a refresh with JS fix it?

indeed, this is not "the good old pal", i was just kidding a little. and: a refresh (in this case: iframe.contentDocument.location.reload();) did not made it.

anyway i learned so far that gecko needs to have some time to learn about a documents iframes. and in my example (currently not linked, i'll have to create the testcase for bugzilla later on) it disappears quite fast. i'll try a setTimeout('anyFunc()',10); as workaround next. unfourtionatly i hope to find a solution w/o javascript, but that's for the testcase then.