- From: Jonas Sicking <jonas@sicking.cc>
- Date: Fri, 2 Jul 2010 01:54:29 -0700
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Chris Wilson <cwilso@microsoft.com>, Boris Zbarsky <bzbarsky@mit.edu>, 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>
On Fri, Jul 2, 2010 at 1:29 AM, Anne van Kesteren <annevk@opera.com> wrote: > 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. Indeed. Seems like having the DOM Events spec say that EventTargets are standalone unless otherwise specified seems like a good idea. / Jonas
Received on Friday, 2 July 2010 09:00:12 UTC