Re: [XHR] send() "stringification mechanisms of the host language"

2007-03-30 Thread Simon Pieters
On Fri, 30 Mar 2007 23:45:47 +0200, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: JavaScript has a toString conversion operation defined on all types. For an HTML div element it would say "[object HTMLDivElement]" or something similar. Ah. Makes sense. Thanks. -- Simon Pieters

Re: [XHR] send() "stringification mechanisms of the host language"

2007-03-30 Thread Maciej Stachowiak
On Mar 30, 2007, at 2:31 PM, Simon Pieters wrote: In the send(data) algorithm, step 3, says: data is not a DOMString or Document The stringification mechanisms of the host language must be used on data and the result must be treated as if data is a DOMString. I'm not sure

Re: [XHR] Uppercasing some HTTP methods

2007-03-30 Thread Anne van Kesteren
On Fri, 30 Mar 2007 23:40:15 +0200, David Håsäther <[EMAIL PROTECTED]> wrote: Simon Pieters wrote: The send(data) algorithm, step 4, says: If method case-insensitively matches GET, POST, HEAD, PUT, DELETE or OPTIONS the user agent must use convert it to its uppercase equivalen

Re: [XHR] Uppercasing some HTTP methods

2007-03-30 Thread David Håsäther
Simon Pieters wrote: The send(data) algorithm, step 4, says: If method case-insensitively matches GET, POST, HEAD, PUT, DELETE or OPTIONS the user agent must use convert it to its uppercase equivalent and let stored method be the result. "... must use convert ..." should probab

[XHR] send() "stringification mechanisms of the host language"

2007-03-30 Thread Simon Pieters
In the send(data) algorithm, step 3, says: data is not a DOMString or Document The stringification mechanisms of the host language must be used on data and the result must be treated as if data is a DOMString. I'm not sure what that means. For instance, if data is an Element, wou

Re: [XHR] Uppercasing some HTTP methods

2007-03-30 Thread Simon Pieters
On Fri, 30 Mar 2007 23:22:53 +0200, Anne van Kesteren <[EMAIL PROTECTED]> wrote: On Fri, 30 Mar 2007 23:18:54 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: The send(data) algorithm, step 4, says: If method case-insensitively matches GET, POST, HEAD, PUT, DELETE or OPTIONS the us

Re: [XHR] Editorial: typos

2007-03-30 Thread Anne van Kesteren
On Fri, 30 Mar 2007 23:08:16 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: Section 2, OPEN: "During this state reqeust headers...", s/reqeust/request/ Section 2, setRequest() algorithm, step 3: "...the user agent must raise a SYNTAX_ERR and abort these steps", should say "...SYNTAX_ERR

Re: [XHR] Uppercasing some HTTP methods

2007-03-30 Thread Anne van Kesteren
On Fri, 30 Mar 2007 23:18:54 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: The send(data) algorithm, step 4, says: If method case-insensitively matches GET, POST, HEAD, PUT, DELETE or OPTIONS the user agent must use convert it to its uppercase equivalent and let stored method

[XHR] Uppercasing some HTTP methods

2007-03-30 Thread Simon Pieters
The send(data) algorithm, step 4, says: If method case-insensitively matches GET, POST, HEAD, PUT, DELETE or OPTIONS the user agent must use convert it to its uppercase equivalent and let stored method be the result. Why not always uppercase method? -- Simon Pieters

[XHR] Editorial: typos

2007-03-30 Thread Simon Pieters
Section 2, OPEN: "During this state reqeust headers...", s/reqeust/request/ Section 2, setRequest() algorithm, step 3: "...the user agent must raise a SYNTAX_ERR and abort these steps", should say "...SYNTAX_ERR exception..." After the send(data) algorithm: "if authentication fails...", s/if

[XHR] "the specification of a proxy"...?

2007-03-30 Thread Simon Pieters
After the send(data) algorithm, there is this paragraph: If the user agent allows the specification of a proxy it should modify the request appropriately; i.e., connect to the proxy host instead of the origin server, modify the Request-Line and send Proxy-Authorization headers as spe

[XHR] Algorithms

2007-03-30 Thread Simon Pieters
In xhr, are the algorithms to be implemented exactly, or can they be implemented in any manner so long as the end result is the same? Please say which in the Conformance section. -- Simon Pieters

Re: [XHR] Test cases

2007-03-30 Thread Simon Pieters
On Fri, 30 Mar 2007 11:27:29 +0200, Anne van Kesteren <[EMAIL PROTECTED]> wrote: On Fri, 30 Mar 2007 11:19:34 +0200, Anne van Kesteren <[EMAIL PROTECTED]> wrote: Presumingly three test cases is not enough to cover all conformance criteria that apply to UAs. Thus, I want to contribute with

Re: [XHR] Test cases

2007-03-30 Thread Anne van Kesteren
On Fri, 30 Mar 2007 11:19:34 +0200, Anne van Kesteren <[EMAIL PROTECTED]> wrote: Presumingly three test cases is not enough to cover all conformance criteria that apply to UAs. Thus, I want to contribute with test cases as part of my review of xhr that I planned to do this weekend. The ex

Re: [XHR] Test cases

2007-03-30 Thread Anne van Kesteren
On Fri, 30 Mar 2007 03:45:45 +0200, Simon Pieters <[EMAIL PROTECTED]> wrote: I found http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequestTestSuite/ which contains three tests, AFAICT. The test cases use ActiveX for IE. The spec doesn't say anything about ActiveX. An implementa