On Tue, 19 Sep 2006 14:01:41 -, Alexey Proskuryakov
[EMAIL PROTECTED] wrote:
I have tried searching the archives, but couldn't find this already
discussed.
The specification defines states 1 and 2 as:
1 Open. The open() method has been successfully called.
2 Sent. The UA successfully
On Tue, 19 Sep 2006 12:59:30 -, Web APIs Issue Tracker
[EMAIL PROTECTED] wrote:
To make XPathNSResolver reusable in Selectors API it has to support a
notion of a default namespace.
Since DOM Level 3 XPath isn't really moving yet one idea would be to
define it in Selectors API and
On Fri, 31 Mar 2006 08:57:48 -, Cameron McCormack [EMAIL PROTECTED]
wrote:
I asked on #webapi the other day what XHR should do if setRequestHeader
is called with strings that contain non-ASCII characters, since that's
not allowed by HTTP. Anne suggested I make a test, so here is one
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
ISSUE-87: invoking open() when readyState is not 0, 1 or 4
http://www.w3.org/2005/06/tracker/webapi/issues/87
Raised by: Anne van Kesteren
On product: XMLHttpRequest
Currently the specificatoin defines open for when readyState is 0 (or
1...) (you go to 1) and If open() is invoked when
