ISSUE-86 - Public View

Throw INVALID_STATE_ERR everywhere, don't or some mix?

State:
CLOSED
Product:
XMLHttpRequest
Raised by:
Anne van Kesteren
Opened on:
2006-09-20
Description:
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).

Note: Some of these links may be accessible only to W3C Members.

Related emails:
  1. ISSUE-86: Throw INVALID_STATE_ERR everywhere, don\\'t or some mix? (from dean+cgi@w3.org on 2006-09-20)
  2. Minutes: WebAPI F2F Session 5, 21 Sept 2006 (from doug.schepers@vectoreal.com on 2006-09-21)
  3. Re: ISSUE-86: Throw INVALID_STATE_ERR everywhere, don\\'t or some mix? (from annevk@opera.com on 2006-09-22)

Related notes:

2006-09-21: Resolved as per Anne's proposal - we throw the exception everywhere (which means work for everyone implementing :\\