On Tue, Sep 11, 2012 at 10:43 PM, Adam Barth w...@adambarth.com wrote:
I'm sorry this thread has taken too long. I've lost all context. If
you'd like to continue this discussion, we'll likely need to start
again.
My main reaction to what you've written is that Chromium's network
stack is
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18852
Summary: FileList says it's a Collection but that doesn't make
sense
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Anne van Kesteren wrote:
On Mon, Sep 10, 2012 at 10:05 AM, Mike Wilson
mike...@hotmail.com wrote:
Thanks. So I understand it is the HTML specification reference
that provides details on this behaviour for the XHR spec.
I'll look further there as its fetching section by itself
doesn't
On Wed, Sep 12, 2012 at 8:35 PM, Mike Wilson mike...@hotmail.com wrote:
On the other hand, in:
https://bugzilla.mozilla.org/show_bug.cgi?id=785243
Firefox implementors say that:
sync XHR spins the event loop, so events (including async
script execution and whatnot) can fire under a sync
I certainly agree that we should define these things clearly. :)
Adam
On Tue, Sep 11, 2012 at 11:44 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Sep 11, 2012 at 10:43 PM, Adam Barth w...@adambarth.com wrote:
I'm sorry this thread has taken too long. I've lost all context. If
you'd
On 9/12/12 7:35 PM, Mike Wilson wrote:
On the other hand, in:
https://bugzilla.mozilla.org/show_bug.cgi?id=785243
Firefox implementors say that:
sync XHR spins the event loop, so events (including async
script execution and whatnot) can fire under a sync XHR call.
That's a comment about
