Can you point me to where? XHR L2 spec says "To dispatch a readystatechange event means that an event with the name readystatechange, with no namespace, which does not bubble and is not cancelable, and which uses the Event interface, is to be dispatched at the XMLHttpRequest object." (end of section 2.2), but doesn't say anything about capturing - effectively raising the issue of event flow without directly mentioning it. DOM L3 Events spec says "This document specifies an event flow for tree-based structures: DOM event flow... applications might reuse the interfaces defined in this document for non-tree-based structures." (Section 1.1.1) DOM L3 spec does describe the event flow as "Each event has an event target, a targeted node in the case of the DOM Event flow, toward which the event is dispatched by the DOM Events implementation." (Section 1.2) I suppose one might consider that this means in the case of XHR, that since no non-tree based structure has been explicitly specified for XHR objects, that the dispatching is indeed directly on to the XHR object, but then it seems redundant and confusing to additionally state that the events do not bubble (but not refer to capturing), rather than simply saying explicitly "There is no event flow outside of dispatching directly to the object."
-----Original Message----- From: Anne van Kesteren [mailto:[email protected]] Sent: Friday, July 02, 2010 9:31 AM To: Jonas Sicking; Chris Wilson Cc: Boris Zbarsky; Brett Zamir; [email protected]; [email protected]; Travis Leithead; Adrian Bateman Subject: Re: Custom DOM events and privileged browser add-ons; Was: Bubbling/Capturing for XHR + other non-DOM objects On Fri, 02 Jul 2010 18:21:31 +0200, Chris Wilson <[email protected]> wrote: > BTW, the XHR spec does not say anything about capture, iirc, just > bubbling - leaving it somewhat ambiguous. It is actually quite explicit as far as I can tell. -- Anne van Kesteren http://annevankesteren.nl/
