Re: DOM3 Events call today/tonight?

On 2/25/09 7:46 PM, Garrett Smith wrote:
> On Wed, Feb 25, 2009 at 8:27 AM, Charles McCathieNevile
> <>  wrote:
>> Hi folks,
>> unfortunately I have not been able to catch up with Doug (a combination of
>> both of us travelling and then I had a minor accident that put me out of
>> commission for a while), so as far as I know we have no agenda planned for
>> tonight's call.
>> The call is booked:
>> Telephone: +1.617.761.6200  meeting code 3663 (DOM3).
>> Pacific time: 11.30am - 1pm
>> Boston time: 2.30pm - 4pm
>> UTC: 1930Z - 2100Z
>> CET: 2030 - 2200
>> If anyone would like to hold a call, please reply to this thread - if there
>> are no replies in the next 90 minutes (by 1900CET, 10am Pacific, 1pm
>> Boston), we will postpone the restart until next week, and Doug and I will
>> coordinate to ensure there is an agenda.
> It might be worth discussing the load event;
> Seems that it is "specified" to fire on Document or Element (instead
> of window).

HTML 5 says that "If the Document is in a browsing context, then queue a 
task to fire a load  event at the Document's Window  object."
And that is what at least Gecko does.

'load' is a special event in many ways. 'load' events dispatched 
somewhere in document (for example for <img>) don't propagate to 
'window'. And the 'load' event which is dispatched to 'window', has 
'document' as its target. This all is required for backwards compatibility.

This is related to


>> sorry about this
> Garrett

Received on Wednesday, 25 February 2009 18:16:50 UTC