- From: Web APIs Issue Tracker <dean+cgi@w3.org>
- Date: Mon, 13 Mar 2006 19:52:52 +0000 (GMT)
- To: public-webapi@w3.org
ISSUE-39: Errors in XHR requests http://www.w3.org/2005/06/tracker/webapi/issues/39 Raised by: Dean Jackson On product: XMLHttpRequest We have yet to resolve what to do with errors in XHR requests, such as lack of network, loops in redirects, etc. There currently isn't interoperable behaviour. Using bogus statusCodes is unnacceptable, as is throwing an exception that can only be caught on the global object. A new value for readyState will break all content that is written expecting there will never be a new value. One suggestion is to return a new value for status (eg. -1) and set statusText to an error message. References: http://lists.w3.org/Archives/Public/public-webapi/2006Mar/att-0092/22-webapi-minutes.html http://www.quirksmode.org/blog/archives/2005/09/xmlhttp_notes_r_2.html
Received on Monday, 13 March 2006 19:52:58 UTC