RE: Custom DOM events and privileged browser add-ons; Was: Bubbling/Capturing for XHR + other non-DOM objects

See, this is exactly why we asked the question - because it seems that behavior is inconsistent, we're not sure what the expectation is.  The fact that the XHR spec says the events do not bubble (but says nothing about capture) is confusing.  DOM L3 Events says "here's what happens for DOM elements," but doesn't say explicitly if NOTHING should happen for non-DOM uses, or if something else should depending on context.

-Chris

-----Original Message-----
From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] 
Sent: Friday, June 25, 2010 9:59 AM
To: Brett Zamir
Cc: Anne van Kesteren; www-dom@w3.org; public-webapps@w3.org; Travis Leithead; Adrian Bateman; Chris Wilson
Subject: Re: Custom DOM events and privileged browser add-ons; Was: Bubbling/Capturing for XHR + other non-DOM objects

On 6/25/10 5:56 AM, Brett Zamir wrote:
> I guess in Firefox the document is all part of one big tree that 
> includes the add-on markup, so propagation is indeed within the same 
> DOM tree

It's not, actually.  In Firefox, an event will bubble from a Window to some object in the browser UI associated with that Window.  This object is the same for a page and all its subframes.

What this object is is effectively an implementation detail.

Note that we plan to keep this behavior as we move to a multi-process architecture, at which point the event will effectively bubble across the process boundary.

-Boris

Received on Tuesday, 29 June 2010 21:37:03 UTC