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

Re: XMLHttpRequest readystatechange events

From: Robin Berjon <robin.berjon@expway.fr>
Date: Mon, 24 Apr 2006 10:59:06 +0200
Message-Id: <C3E239F5-75B9-460C-9638-D054B5012504@expway.fr>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
To: Boris Zbarsky <bzbarsky@mit.edu>

On Apr 24, 2006, at 01:45, Boris Zbarsky wrote:
> Robin Berjon wrote:
>>> At the moment, Gecko allows adding a single "onreadystatechange"  
>>> listener that's notified of changes in readyState.  We would like  
>>> to add the ability to add such listeners via addEventListener;  
>>> the event name would be "readystatechange".
>> So basically this would amount to supporting EventTarget on XHR,  
>> right?
>
> We already do that -- "load" and "error" events can already be  
> added via addEventListener.  The question I have is whether there  
> are any obvious problems with also allowing addition of  
> "readystatechange" event listeners (and firing said events), in  
> terms of interaction with other XMLHttpRequest implementations and  
> with planned future work by the WG.

Ah okay, well as Björn pointed out, adding a new event in no  
namespace is definitely treading on the WG's toes. Adding it in your  
own namespace would avoid potential clashes.

-- 
Robin Berjon
    Senior Research Scientist
    Expway, http://expway.com/
Received on Monday, 24 April 2006 09:12:44 GMT

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