iframe does not render in a seperate thread as the main page




13 years ago
13 years ago


(Reporter: apota, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

In IE, if I have a page that has an iframe, the loading of the page is
independent of the loading of the iframe i.e. the page loads regardless of
whether the iframe loads or not. 

I noticed that this is not the case with Firefox. The iframe loads at the same
time as the page containing it. 

Is this expected behavior?. I believe the iframe is just like a frame and like a
regular frame it should load independently of the main page containing it.

Reproducible: Always

Steps to Reproduce:
Create a wrapper.html page. Type the following in the wrapper page.

  function setStatus () {
   document.getElementById("help").innerHTML = "&nbsp;";

  function setText (txt) {
   document.getElementById("panel3").innerHTML = txt;

<span id="help">&nbsp;</span><br>
<div id="panel3"></div>

  document.getElementById("help").innerHTML = "Loading. Please wait...";

<iframe style="display:none" id="loader" name="loader"

Create another file lotofmarkup.html. Type the following in that file

<!-- Add a table with 1000 rows here  -->


The basic idea of this example is that when I load wrapper.html. It loads first
and the iframe containing lotofmarkup.html loads independently of wrapper.html
and upon a complete load it updates the status label on the wrapper.html 

The above behavior happens in IE not in Firefox. In Firefox, wrapper.html does
not load until lotofmarkup.html finishes loading.

Actual Results:  
See "Steps to Reproduce" to see a complete description

Expected Results:  
See "Steps to Reproduce" to see a complete description
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.