xul iframes don't execute onload handlers when if ran via chrome url from command line




14 years ago
13 years ago


(Reporter: ed, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)



(2 attachments)

423 bytes, application/vnd.mozilla.xul+xml
458 bytes, application/octet-stream


14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705)
Build Identifier: 

It appears that an iframe load event hander, whether specified via onload= or 
via addEventListener, doesn't work in an XUL window when run from the command 
line with with firefox.exe -chrome

Reproducible: Always

Steps to Reproduce:
1. Create xul file (test.xul):

<?xml version="1.0"?>
<window id="main-window" title="Test" orient="vertical" width="640" 
	<script src="test.js"/>

	<button label="Test" oncommand="testIFrame();" />
	<textbox id="my-text" multiline="true" flex="1" value="Sample text here 
Sample text here Sample text here" />
	<iframe id="my-frame" src="" flex="2"  />


2. Create script file (test.js):

function testIFrame() {
	var my_text = document.getElementById("my-text");
	var my_frame = document.getElementById("my-frame");
	my_text.value = "Loading iframe";
	my_frame.addEventListener("load", testIFrame_loaded, false);
	my_frame.setAttribute("src", "http://www.google.com");

function testIFrame_loaded() {
	var my_text = document.getElementById("my-text");
	my_text.value = "iframe is loaded";

3. Set up as chrome

4. Try from address bar and from command line
Actual Results:  
When the file is opened from the address bar, the load event handler is called
When the file is opened from the -chrome command line, the event handler is not 

Expected Results:  
Event handler should work in both cases

Comment 1

14 years ago
Created attachment 179220 [details]
Testcase xul file

Comment 2

14 years ago
Created attachment 179221 [details]
Testcase script file
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050401

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.