On Tue, Jun 21, 2011 at 12:30 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/21/11 3:01 PM, Darin Fisher wrote:
Isn't there already a signal to tell you when response headers are
available?
Yes; I believe the readystate changes at this point and onreadystatechange
is fired.
Isn't it a
Hey Maciej, Kenneth, opinions? (Or know anyone who does.)
On Thu, 17 Mar 2011 16:43:11 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
http://www.w3.org/TR/XMLHttpRequest2/ section 3.6.9 near the end says:
If the request entity body has been successfully uploaded and the
upload complete
Hmm... this is curious. I'm not sure that the Chrome behavior is
intentional. I need
to investigate further.
Isn't there already a signal to tell you when response headers are
available? Isn't it a
bit redundant for the upload complete notification to be tied to the same
signal?
To support
On 6/21/11 3:01 PM, Darin Fisher wrote:
Isn't there already a signal to tell you when response headers are
available?
Yes; I believe the readystate changes at this point and
onreadystatechange is fired.
Isn't it a bit redundant for the upload complete notification to be tied to the
same
http://www.w3.org/TR/XMLHttpRequest2/ section 3.6.9 near the end says:
If the request entity body has been successfully uploaded and the
upload complete flag is still false, queue a task to run these
substeps:
We have implemented this in Gecko, but the result seems to be some
confusion
