33106 2010-01-02 09:39:20 -0800 'load' events fire with event.eventPhase set to '0' instead of '2' AT_TARGET 2010-01-02 13:31:49 -0800 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) PC OS X 10.5 RESOLVED WORKSFORME P2 Normal --- 0 diego.perini webkit-unassigned ap oldest_to_newest 176326 0 diego.perini 2010-01-02 09:39:20 -0800 I tested this both on Safari Version 4.0.4 (6531.21.10) and Version 3.1.2 (5525.20.1) I noticed that the 'load' event will fire with event.eventPhase set to '0' instead of '2' AT_TARGET. This happens in Safari both using DOM2 or DOM0 registration. Doesn't happen in any other tested browser. Simple test I used: DOM2 window.addEventListener('load', function(e) { alert("event.eventPhase: " + e.eventPhase + "\nphase should be: 2"); }, false); DOM0 window.onload = function(e) { alert("event.eventPhase: " + e.eventPhase + "\nphase should be: 2"); }; from what I understand the possible values are 1, 2 and 3 ... If I recall 0 was for custom events. 176349 1 ap 2010-01-02 11:50:36 -0800 I can reproduce with shipping Safari/WebKit, but not with a ToT WebKit build - possibly fixed in <http://trac.webkit.org/changeset/48701>. Please test with a nightly build from <http://nightly.webkit.org>. 176381 2 diego.perini 2010-01-02 13:31:49 -0800 Alexey, that was fast ;-) Solves for me, when the 'load' event fires on window object, 'eventPhase' property is now correctly AT_TARGET (2). Tested with nightly build (r52686). Thank you for your precious help.