296269 - Opening XUL iframe with missing .css file prevents onload event from firing when visiting page first time

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Tony Wells]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412 (KHTML, like Gecko) Safari/412
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

If you have a XUL page which has an iframe, and you set the src of that iframe to a XUL page that has a 
reference to a .css file that doesn't exist, the onload handler won't be called on the first visit to the XUL 
page in the iframe.  If you set the src of the iframe to that XUL page again, onload event will fire.

This has the effect that if you use an iframe to diplay content in a XUL app, and that page has a 
missing .css file, the page "doesn't work" the first time you try to load it.  Easy to fix the XUL, but probably 
a real pain for the newbies to find.

Reproducible: Always

Steps to Reproduce:
1. Easy to reproduce, the "Details" section should get you there.

Actual Results:  
First time you load a XUL page in an iframe, if there is a missing .css file, onload handler doesn't get 
called.

Expected Results:  
The function referenced in the onload= in the window element should work the first time the XUL page is 
loaded in the iframe whether there is a missing .css file or not.

Comment 1

[Peter van der Woude [:Peter6]]

simple testcase please

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.