105632 - window.onload event does not appear to work on NT Server

Status: VERIFIED INVALID

(Core :: DOM: Events, defect)

Description

[rvj]

I have recently started testing my xul app on a NT server and found that 
window.onload = function () event does not fire.

I understand NT workstation and NT server use common core code so I am a little 
surprised.  I have attached a XUL testcase which should display the message 
file loaded.

Comment 1

[rvj]

Attachment: xul testcase

Comment 2

[serge (gone)]

yes, I run in to this problem too, but the next seems work
> window.frames[0].window.addEventListener('onload', alert('file loaded'), false);

Comment 3

[Fabian Guisset]

Confirmed. I have absolutely no idea why .onload doesn't work while
addEventListener works.
Note that this is using 0.9.6 on win2k.
Marking NEW.

Comment 4

[Johnny Stenback (:jst)]

Window (and frame) event handler are cleared when a new page is loaded into the
window (or frame), except in the case when the page being replaced is
"about:blank", window.addEventListener("load") (note, not "onload") should be no
different than window.onload=...

Use nsIWebProgress, or iframe.onload to know when an iframe has loaded, don't
mess with event handlers *in* the iframe content from outside the iframe content.

INVALID. (joki, reopen if you disagree)

Comment 5

[Vladimir Ermakov]

The addEventListener is not actually fired but because of bug 119072 which I
found while investigating this the alert box is still shown...

I still have doubts about this though, isnt frames[0].window still outside the
frame content, while frames[0].document would be inside the content?

If it is so the event handlers should be fired.

Comment 6

[Vladimir Ermakov]

actually if it was true window.onload, once set, would be called every time you
go to any page, and the only way to reset it would be to close the window...

verifying invalid