[whatwg] ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events]
giecrilj at stegny.2a.pl
Tue Jul 29 11:59:49 PDT 2008
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).
From: whatwg-bounces at 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 "188.8.131.52. Events and the Window object"  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.
Web Applications Working Group Issue Tracker wrote:
> ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of
events and the Window object? [DOM3 Events]
> 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:
> ....and DOM3 Events says this:
More information about the whatwg