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: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Thu, 07 Aug 2008 22:18:27 +0300
Message-ID: <489B4A83.50309@helsinki.fi>
To: Web Applications Working Group WG <public-webapps@w3.org>
CC: Ian Hickson <ian@hixie.ch>



Web Applications Working Group Issue Tracker wrote:
> ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events]
> 
> http://www.w3.org/2008/webapps/track/issues/44
> 
> Raised by: Ian Hickson
> On product: DOM3 Events
> 
> We need to decide whether HTML5 or DOM3 Events (or another spec) defines how events interact with the Window object that browsers have.
> 
> Right now HTML5 says this:
> http://www.whatwg.org/specs/web-apps/current-work/#events0
> ....and DOM3 Events says this:
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-flow
> 


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]


-Olli


[1] http://www.w3.org/TR/DOM-Level-2-Views/
[2] http://www.whatwg.org/specs/web-apps/current-work/#window
Received on Thursday, 7 August 2008 19:21:05 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT