- From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
- Date: Tue, 29 Jul 2008 20:59:49 +0200
I am not sure where it is relevant but I remember from learning Borland Paradox that events are dispatched to window first so that the window can intercept them universally and then they bubble bottom up if not intercepted. This feature is called "global grab" (if the window decides to handle the event exclusively) or "global filter" (if the event is allowed to pass to the control). Chris -----Original Message----- From: whatwg-bounces@lists.whatwg.org [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Olli Pettay Sent: Tuesday, July 29, 2008 8:51 PM To: Web Applications Working Group WG; whatwg List Subject: Re: [whatwg] ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events] Chapter "5.4.4.3. Events and the Window object" [1] says that event is also dispatched to window before (and after) dispatching to DOM nodes. I'd rather say window object is part of the event target chain (unfortunately load event is a special case), so events automatically propagate from document to window. No need to re-dispatch anything. (This is how gecko works ;) ) Or perhaps that is what the text is trying to say, but it should probably talk about event propagation, not about dispatching to window. -Olli [1] http://www.whatwg.org/specs/web-apps/current-work/#events0 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#event s-Events-flow > > > > >
Received on Tuesday, 29 July 2008 11:59:49 UTC