Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

2007-03-05 Thread Anne van Kesteren
Hi, Hixie forwarded your comments to me as I'm now the editor of the XMLHttpRequest specification: http://www.w3.org/TR/XMLHttpRequest/ On Wed, 22 Jun 2005 10:44:39 +0200, Hallvord Reiar Michaelsen Steen <[EMAIL PROTECTED]> wrote: > getAllResponseHeaders() > If the readyState attribute

Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

2006-08-10 Thread Anne van Kesteren
On Mon, 30 Jan 2006 13:47:34 +0100, Hallvord R M Steen <[EMAIL PROTECTED]> wrote: By the way, about "getResponseHeader" the sentence: If no headers of that name were received, then returns the empty string should be fixed to say "returns null". Fixed. Please raise new issues on [EMAIL PRO

Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

2006-01-30 Thread Hallvord R M Steen
By the way, about "getResponseHeader" the sentence: > If no headers of that name were received, then returns the > empty string should be fixed to say "returns null". -- Hallvord R. M. Steen

Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

2006-01-25 Thread Hallvord Reiar Michaelsen Steen
On 22 Jun 2005 at 10:44, Hallvord Reiar Michaelsen Ste wrote: > > 2) This is not what UAs actually do. IE and FF throw an exception and > > Opera returns an empty string. > > Same applies to getResponseHeader, except that the spec actually says > "return empty string" rather than null here.

Re: [whatwg] XMLHttpRequest: getAllResponseHeaders

2006-01-25 Thread Hallvord Reiar Michaelsen Steen
On 22 Jun 2005 at 10:24, Hallvord Reiar Michaelsen Ste wrote: >> getAllResponseHeaders() >> If the readyState attribute has a value other than 3 (Receiving) or >> 4 (Loaded), returns null. > 1) This seems a bit inconsistent since the spec says that accessing > status and statusText out of order