96926 - onLoad fired before document has finished loading

Status: VERIFIED DUPLICATE of bug 93015

(Core :: DOM: Events, defect)

Description

[Jason Henriksen]

Under mozilla 0.9.3 it appears that my document.body.onLoad event handler is
being called well before the document has loaded.  As I understand it, the
onLoad event should not be fired until the entire page and all of it's images
are loaded and displayed.

Comment 1

[Jason Henriksen]

This only happens if I do the following:

document.location.replace("foo.html");
document.onload = alert("e");

The "e" appears before the document is loaded.

Comment 2

[Vladimir Ermakov]

Made a simple testcase with your code and it worked exactly the same as in IE.... 

Comment 3

[Ashley Bischoff (blog at handcoding.com)]

Vladimire: In the interest of triaging Unconfirms, should this bug be marked
WONTFIX, INVALID, NEW, or what?

Comment 4

[Jason Henriksen]

I have been away for a couple of days, but I'm certain that I can make a test 
case to recreate this bug.  I'll try to have it for you later today / tomorrow.
Until then, Unconfirmed seems the most correct.

Comment 5

[Jason Henriksen]

Attachment: shows onLoad weirdness with moz/netscape (zip contains html)

Comment 6

[Jason Henriksen]

I've just attached a test case for this bug that illustrates what I'm trying to
do.  However, I've discovered that the problem also occurs in Netscape 4.75. 
Maybe the code I've written is wrong, but it seems to match the examples so I'm
stymied.

I'm using mozilla 0.9.3

Comment 7

[Mike Kaply [:mkaply]]

I just put an example of this at:

http://www.kaply.com/work/onload.html

I can't really reduce the testcase yet.

I put two alerts in that show the problem.

There is an INPUT field whose value is set to 2.

The alert shows this INPUT fields value.

On 4.x it properly shows 2, on Mozilla, it shows 0.

Comment 8

[Ashley Bischoff (blog at handcoding.com)]

Marking NEW.

Comment 9

[saari (gone)]

dupe of 93015 or vice versa?

Comment 10

[saari (gone)]

yes, dup of 93015

*** This bug has been marked as a duplicate of 93015 ***

Comment 11

[Vladimir Ermakov]

verifying