W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2011

Re: ISSUE-131 (defaultView load ): Define load event to fire on defaultView [DOM3 Events]

From: Jacob Rossi <Jacob.Rossi@microsoft.com>
Date: Wed, 17 Aug 2011 00:41:05 +0000
To: "www-dom@w3.org" <www-dom@w3.org>
CC: "hallvord@opera.com" <hallvord@opera.com>, "annevk@opera.com" <annevk@opera.com>, "Olli@pettay.fi" <Olli@pettay.fi>, "simonp@opera.com" <simonp@opera.com>
Message-ID: <D0BC8E77E79D9846B61A2432D1BA4EAE0341AAB4@TK5EX14MBXC287.redmond.corp.microsoft.com>
Hi folks,

I realize now that the original change I made to cover this issue was not very clear. I think we're all really in agreement here:

HTML5 defines the load event to not include the defaultView in the propagation path when it is fired for resources within the document (e.g. images). [1] All major implementations match this behavior.

So to clarify, I've updated the original note to now say this:

"Note: for legacy reasons, load events for resources inside the document (e.g., images) do not include the defaultView in the propagation path in HTML implementations. See [HTML5] for more information."

Let me know if you have any additional comments on the change.

Thanks,

Jacob

[1] http://dev.w3.org/html5/spec/Overview.html#events-and-the-window-object

================================================
From: Hallvord R. M. Steen <hallvord@opera.com>
Date: Mon, 11 Oct 2010 15:04:52 +0900
To: "Doug Schepers" <schepers@w3.org>, "Anne van Kesteren" <annevk@opera.com>
Cc: www-dom@w3.org, "Simon Pieters" <simonp@opera.com>
Message-ID: <op.vkeduejla3v5gv@hr-opera.oslo.opera.com>
On Fri, 08 Oct 2010 16:31:37 +0900, Anne van Kesteren <annevk@opera.com>  
wrote:

>>> Note: for legacy reasons, the load event does not propagate to the
>>> defaultView in HTML implementations.
>>
>> My suggestion would be something like
>>
>> Note: for legacy reasons, load events dispatched when resources inside  
>> the document are loaded do not propagate to the defaultView in HTML  
>> implementations. The load event for the document itself is dispatched  
>> on the defaultView as described in [HTML5].
>
> Isn't that wrong? Because all events are dispatched on defaultView as  
> per HTML5.

I'm not entirely sure what you think is wrong. In any case, the  
clarification in my first sentence (explicitly mention 'resources inside  
the document') is more important. The second sentence could for example  
say "For information on how the document's load event is dispatched, see  
[HTML5]."

-- 
Hallvord R. M. Steen, Core Tester, Opera Software
http://www.opera.com http://my.opera.com/hallvors/




From: Hallvord R. M. Steen <hallvord@opera.com>
Date: Mon, 11 Oct 2010 15:04:52 +0900
To: "Doug Schepers" <schepers@w3.org>, "Anne van Kesteren" <annevk@opera.com>
Cc: www-dom@w3.org, "Simon Pieters" <simonp@opera.com>
Message-ID: <op.vkeduejla3v5gv@hr-opera.oslo.opera.com>
On Fri, 08 Oct 2010 16:31:37 +0900, Anne van Kesteren <annevk@opera.com>  
wrote:

>>> Note: for legacy reasons, the load event does not propagate to the
>>> defaultView in HTML implementations.
>>
>> My suggestion would be something like
>>
>> Note: for legacy reasons, load events dispatched when resources inside  
>> the document are loaded do not propagate to the defaultView in HTML  
>> implementations. The load event for the document itself is dispatched  
>> on the defaultView as described in [HTML5].
>
> Isn't that wrong? Because all events are dispatched on defaultView as  
> per HTML5.

I'm not entirely sure what you think is wrong. In any case, the  
clarification in my first sentence (explicitly mention 'resources inside  
the document') is more important. The second sentence could for example  
say "For information on how the document's load event is dispatched, see  
[HTML5]."

-- 
Hallvord R. M. Steen, Core Tester, Opera Software
http://www.opera.com http://my.opera.com/hallvors/
Received on Wednesday, 17 August 2011 00:41:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:08 GMT