- From: Jonas Sicking <jonas@sicking.cc>
- Date: Fri, 08 Aug 2008 00:10:44 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: olli@pettay.fi, Web Applications Working Group WG <public-webapps@w3.org>
Ian Hickson wrote: > On Thu, 7 Aug 2008, 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. > > Is that any load event, or only specific load events? (i.e. is it a > characteristic of the bubbling/capture process, or the events that are > fired by certain circumstances like the end of parsing or an image being > fetched from the network?) If the latter, it would be useful if the DOM3 > Events spec could provde a hook for the HTML5 spec to annotate certain > events as being affected by this exception. I think it is all 'load' events except the one fired for the finished load of the actual page. I.e. loads for images, stylesheets, plugins, etc had to not reach the Window object. I'm uncertain if iframe loads reach the Window or not. / Jonas
Received on Friday, 8 August 2008 07:12:20 UTC