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
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
On Sun, Sep 9, 2012 at 6:33 PM, Mike Wilson mike...@hotmail.com wrote:
I didn't find statements directly addressing this in
http://www.w3.org/TR/XMLHttpRequest/
or
http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resourc
es.html
but maybe there are indirect relationships
Anne van Kesteren wrote:
On Sun, Sep 9, 2012 at 6:33 PM, Mike Wilson
mike...@hotmail.com wrote:
I didn't find statements directly addressing this in
http://www.w3.org/TR/XMLHttpRequest/
or
http://www.whatwg.org/specs/web-apps/current-work/multipage/fe
tching-resourc
es.html
but
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 directly express the relationship
On 09/09/2012 06:33 PM, Mike Wilson wrote:
Is it defined how the browser should behave wrt calling
unrelated event handlers in user code during synchronous
XHR requests? (with unrelated I refer to events that are
not related to the ongoing synchronous request itself)
I didn't find statements
