W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

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

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 02 Jul 2010 10:29:55 +0200
To: "Chris Wilson" <cwilso@microsoft.com>, "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: "Brett Zamir" <brettz9@yahoo.com>, "www-dom@w3.org" <www-dom@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>, "Travis Leithead" <travil@microsoft.com>, "Adrian Bateman" <adrianba@microsoft.com>
Message-ID: <op.ve7i7pqm64w2qv@annevk-t60>
On Wed, 30 Jun 2010 22:39:48 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 6/29/10 2:36 PM, Chris Wilson wrote:
>> See, this is exactly why we asked the question - because it seems that  
>> behavior is inconsistent, we're not sure what the expectation is.
>
> Note that the Firefox behavior I described is irrelevant to  
> specification efforts, because it's not visible to web pages....
>
> I think Anne answered the question, in any case: the XHR event target  
> chain only contains the XHR object itself and nothing else.  If the spec  
> doesn't say that explicitly, it should.

I do not think the XMLHttpRequest specification should state that to be  
honest. If that is at all unclear from the current specifications (and I  
am not particularly convinced) that should be clarified in DOM Events.  
There are plenty of objects around that implement EventTarget. Saying for  
every single one of them they are standalone is make work.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Friday, 2 July 2010 08:30:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:39 GMT