W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: ISSUE-72: should XMLHttpRequest be an EventTarget?

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 07 Apr 2006 17:56:52 -0700
Message-ID: <44370A54.5000900@sicking.cc>
To: Web APIs WG <public-webapi@w3.org>

Web APIs Issue Tracker wrote:
> ISSUE-72: should XMLHttpRequest be an EventTarget?
> 
> http://www.w3.org/2005/06/tracker/webapi/issues/72
> 
> Raised by: Anne van Kesteren
> On product: XMLHttpRequest
> 
> I know we agreed to not do this for version 1.0 during our F2F (Oslo, 2006), but
> I'd like to revisit it given that there's at least one implementation which is
> doing this and it makes a lot more sense for other languages besides ECMAScript.
> Did I mention it just makes a lot of sense?

What is the advantage of doing this now as opposed to doing it in a 
version 2?

I can see two advantages:

1. It means we can add a pile of other features like onload, onerror
    onprogress and so on.

However, this is straying far from the original intent of the spec which 
was to define what already works.

2. It solves the problem of "what type is onreadystatechange in the idl"

It does feel like this is a pretty poor argument. We would be going 
against the original intent of the spec for what feels like editorial 
reasons. If this is the only reason then I'd like to find another solution.

/ Jonas
Received on Saturday, 8 April 2006 00:57:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT