W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

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

From: Simon Pieters <simonp@opera.com>
Date: Wed, 06 Oct 2010 21:19:00 +0200
To: "Hallvord R. M. Steen" <hallvord@opera.com>, "Doug Schepers" <schepers@w3.org>
Cc: www-dom@w3.org
Message-ID: <op.vj549yxtidj3kv@simon-pieterss-macbook.local>
On Wed, 06 Oct 2010 20:29:49 +0200, Doug Schepers <schepers@w3.org> wrote:

> Hi, Simon, Hallvord-
>
> Hallvord R. M. Steen wrote (on 9/16/10 10:35 PM):
>> On Thu, 16 Sep 2010 16:33:54 +0900, Anne van Kesteren <annevk@opera.com>
>> wrote:
>>
>>>> The text about not-propagating to defaulView doesn't talk about where
>>>> the event is dispatched but about what happens to load events which  
>>>> are
>>>> dispatched to Document or Element.
>>>
>>> Yeah, HTML5 already defines when and when not elements are to be
>>> dispatched on Window. I do not think DOM Level 3 Events needs to be
>>> concerned with that.
>>
>> It would be nice if the text was clearer (and perhaps referenced HTML5
>> for the window case) - as-is, I found it confusing too.
>
> What would your suggested text be for the clarification, and can you  
> please point me to the relevant sections of HTML5?

For the case of the load event, step 8 in  
http://www.whatwg.org/specs/web-apps/current-work/complete/the-end.html#stop-parsing

-- 
Simon Pieters
Opera Software
Received on Wednesday, 6 October 2010 19:20:07 GMT

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