A bug in FF3's sync XHRs ?

Discussion in 'Javascript' started by Jorge, Aug 31, 2008.

  1. Jorge

    Jorge Guest

    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.
     
    Jorge, Aug 31, 2008
    #1
    1. Advertising

  2. Jorge

    GArlington Guest

    On Aug 31, 1:33 pm, Jorge <> wrote:
    > 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...
     
    GArlington, Sep 1, 2008
    #2
    1. Advertising

  3. Jorge

    Jorge Guest

    On Sep 1, 1:27 pm, GArlington <> wrote:
    >
    > 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.
     
    Jorge, Sep 2, 2008
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Travis Newbury

    FF3 anyone?

    Travis Newbury, Jun 18, 2008, in forum: HTML
    Replies:
    65
    Views:
    1,934
    Chris F.A. Johnson
    Jun 23, 2008
  2. dorayme

    Re: FF3 - Better or Not?

    dorayme, Jun 22, 2008, in forum: HTML
    Replies:
    1
    Views:
    319
    dorayme
    Jun 22, 2008
  3. Eris of Stronghold [STRM]

    Absolute Image Positioning in FF3.5 vs IE8

    Eris of Stronghold [STRM], Oct 1, 2009, in forum: HTML
    Replies:
    1
    Views:
    959
  4. Trans
    Replies:
    2
    Views:
    495
    Trans
    Dec 12, 2005
  5. Hamish Campbell

    FF3 Array Sort Bug?

    Hamish Campbell, Jun 10, 2009, in forum: Javascript
    Replies:
    7
    Views:
    151
    Hamish Campbell
    Jun 10, 2009
Loading...

Share This Page