W3C home > Mailing lists > Public > public-webapi@w3.org > February 2007

Re: XMLHttpRequest is an EventTarget ?

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Tue, 13 Feb 2007 19:30:45 -0000
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.tnpchjz3jz3wb9@dragast>

Na , Anne van Kesteren <annevk@opera.com> escreveu:

> On Tue, 13 Feb 2007 20:08:53 +0100, Joćo Eiras <joao.eiras@gmail.com>  
> wrote:
>> The current XMLHttpRequest WD states that the XMLHttpRequest interface  
>> implements the EventTarget interface
>> http://www.w3.org/TR/XMLHttpRequest/#xmlhttprequest
>> In DOM 3 Events, the EventTarget interface defines 5 methods
>> http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTarget
>> which are addEventListener, addEventListenerNS, removeEventListener,  
>> removeEventListenerNS, and dispatchEvent.
>> So far I'm not aware of any current implementation supporting these  
>> methods for the XMLHttpRequest object, except for Gecko.
>
> Yup.
>
>
>> At the same time, the events section
>> http://www.w3.org/TR/XMLHttpRequest/#events
>> mentions that the readystate event object must implement the Event  
>> interface, yet there's still nothing which instructs how to fill the  
>> object.
>
> readystatechange event, even.
>
>
>> Like, which is the event.target, currentTarget property supposed to  
>> hold ?
>
> That's specified by DOM Level 3 Events.
>
>
>> Then, and again, only Gecko passes an Event object to the readystate  
>> listener. No other implementations do.
>>
>> After these considerations, must the interface really implement the  
>> EventTarget interface ?
>
> Yes.
>
>

Then you'll have to convince the other implementors, including Microsoft,  
to add these changes.
Good luck.
Received on Tuesday, 13 February 2007 19:31:08 GMT

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