A bug in FF3's sync XHRs ?

[Jorge]

Either a synchronous call isn't what I believe it to be, or there's a
bug in FF3 :

IOW : Why does the onclick handler of the button "SYNC" return (in
FF3) before the XHR has completed ?

Click it several times in a row, and it will post several concurrent
XHRs ...

http://preview.tinyurl.com/5eu3ll

?

--
Jorge.

[GArlington]

On Aug 31, 1:33*pm, Jorge <jo...@jorgecha morro.comwrote:

Either a synchronous call isn't what I believe it to be, or there's a
bug in FF3 :

IOW : Why does the onclick handler of the button "SYNC" return (in
FF3) before the XHR has completed ?

Click it several times in a row, and it will post several concurrent
XHRs ...

http://preview.tinyurl.com/5eu3ll

?

--
Jorge.

Because of luck of debugging info in sync request (in your link) I can
not say for sure what is happening, but by the look of it, the sync
request is being submitted in async mode and processing continues...
Somebody mentioned a bug in FF (3?) with sync mode AJAX requests in
your previous thread... Maybe this is it...

[Jorge]

On Sep 1, 1:27*pm, GArlington <garling...@tis cali.co.ukwrote :

>
Because of luck of debugging info in sync request (in your link) I can
not say for sure what is happening, but by the look of it, the sync
request is being submitted in async mode and processing continues...

Yes, that's what is happening.

Here's the code of the SYNC button :

sync.onclick= function () {
var a, xhr= new XMLHttpRequest( );
xhr.open("GET", "xhrData.txt?"+ Math.random(), ** false ** );
xhr.send(null);
//dummy do-something-else-just-in-case before returning
//See cljs thread 2
a= 1;
};

If you can monitor the network traffic you'll see that pressing it
once produces a traffic of x (KB/s), pressing it twice yields 2x, etc.
IOW: the synchronous XHRs are being posted asynchronous and
concurrently.

--
Jorge.