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

Re: Exceptions thrown by XMLHttpRequest.responseXML and XMLHttpRequest.responseText

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 25 Feb 2008 14:12:54 +0100
To: "Geoffrey Garen" <ggaren@apple.com>
Cc: public-webapi@w3.org
Message-ID: <op.t620bsh264w2qv@annevk-t60.oslo.opera.com>

On Fri, 15 Feb 2008 18:27:03 +0100, Geoffrey Garen <ggaren@apple.com>  
wrote:
> 3. This specification does not match any shipping version of Internet  
> Explorer, which throws exceptions in some of these conditions, but not  
> all. (The specifics here are a little weird, so I'll leave them out.)

If you have the specifics available please share them. Testing a bit  
further it seems my reverse engineering was a bit flaky, responseText does  
throw for me, but responseXML does not:

   http://tc.labs.opera.com/apis/XMLHttpRequest/responseXML/017.htm
   http://tc.labs.opera.com/apis/XMLHttpRequest/responseText/004.htm


> Would you be willing to consider editing the XMLHttpRequest spec to  
> match this behavior?

Unless new information becomes available my plan is to make responseText  
never return null. Decoding will always work, invalid byte sequences are  
simply to be replaced with U+FFFD characters (similar to other APIs).  
responseText will return the empty string before readyState equals  
LOADING. responseXML will return null until readyState equals DONE.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Monday, 25 February 2008 13:08:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 25 February 2008 13:08:18 GMT