W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events]

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 8 Aug 2008 01:22:54 -0700
Cc: Ian Hickson <ian@hixie.ch>, olli@pettay.fi, Web Applications Working Group WG <public-webapps@w3.org>
Message-Id: <4E86BBA0-A80D-4A8A-93E5-8D2ADCAF322B@apple.com>
To: Jonas Sicking <jonas@sicking.cc>

On Aug 7, 2008, at 11:27 PM, Jonas Sicking wrote:

> Ian Hickson wrote:
>> On Thu, 7 Aug 2008, Olli Pettay wrote:
>>> Could we actually just say that if document implements  
>>> DocumentView interface and .defaultView isn't null and implements  
>>> EventTarget, the event propagates to .defaultView. So in that case  
>>> defaultView becomes the root of the event target chain (if the  
>>> target of the event is bound to document). No need to mention  
>>> Window, since AbstractView is already defined in DOM2 Views[1].  
>>> HTML5 defines that AbstractView must also implement Window and  
>>> EventTarget interfaces. [2]
>> Fine by me, so long as the result is compatible with most UAs.
> One very unfortunate thing is that if i recall correctly the Window  
> object never takes part in the EventTarget chain for the 'load'  
> event. But does for all other events. This was because a lot of  
> sites broke when we tried to bubble 'load' to the Window.

I think it is best to special-case the 'load' event. We have this same  
quirk in WebKit.

Received on Friday, 8 August 2008 08:23:37 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:11 UTC