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

Re: ISSUE-58: XMLHttpRequest.abort() should just reset the object

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 06 Apr 2006 11:41:06 +0200
To: "Jonas Sicking" <jonas@sicking.cc>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.s7kyisj964w2qv@id-c0020.oslo.opera.com>

On Thu, 06 Apr 2006 11:28:09 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>>> If that is indeed true we need to fix it I agree. Is there a sensible  
>>> value we could set .status to for example?
>>
>> Lets keep .status an HTTP status code. What about dispatching an abort  
>> event on the object as I suggested? Not sure if that's appropriate for  
>> this version though...
>
> We have already talked about setting .status to -1 in some error  
> conditions. Aborting is arguably an error condition.

I don't like that idea. I believe we also opted not to do it given that  
people might depend on the way .status acts now in certain error  
conditions. It also makes the attribute unnecessary complex.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Thursday, 6 April 2006 09:41:20 GMT

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