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

ISSUE-86: Throw INVALID_STATE_ERR everywhere, don\'t or some mix?

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Wed, 20 Sep 2006 13:43:34 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060920134334.CCBD1BDA8@w3c4.w3.org>


ISSUE-86: Throw INVALID_STATE_ERR everywhere, don't or some mix?

http://www.w3.org/2005/06/tracker/webapi/issues/86

Raised by: Anne van Kesteren
On product: XMLHttpRequest

The current specification tells user agents to throw the INVALID_STATE_ERR for 
setRequestHeader(), send(), status and statusText.

It tells you to do something different for getResponseHeader(), 
getAllResponseHeaders(), responseText and responseXML.

Internet Explorer throws an exception everytime. Other browsers are less 
consistent and follow the specification in some cases and not in others.

My proposal is to throw an exception (INVALID_STATE_ERR) for every member where 
this is relevant (as has been suggested before on this list).
Received on Wednesday, 20 September 2006 13:43:48 GMT

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