The setTimeout() calls make the test case too complex, esp if timing is an issue.
Firebug has no control over the order of setTimeout or net events other than by slowing down (eg breakpoints) the execution. If you have Firebug enabled for Script and have the script-limiter set to 'all', then eval() will take a lot more time. This is something like 50x, it's a lot. Nothing about the eval() call timing is standard as far as I know, so if the timing alone breaks your code then its probably something that will bite you sooner or later. You can try setting the script-limiter to "static" (next to the filelist on the Script panel) jjb On Nov 14, 8:56 am, Jordan Brough <[EMAIL PROTECTED]> wrote: > Hi John, > The real-life issue I'm having is with the fileQueued callback from > SWFUpload on multiple files (gets called several times in a row for > each file selected). I'm not sure how to replicate this type of > behavior without using setTimeout. Any ideas? Is this something > inherent in setTimeout? Are javascript methods allowed to be > 'paused' (and allow others to continue) if they have been called > during setTimeout? I haven't been able to replicate w/o setTimeout so > far, but I can keep trying if it's impossible to debug otherwise. > > This is from code that I inherited and I'm getting rid of the 'eval' > calls anyway, but I thought you might like to know about the issue. > Might cause some real debugging headaches, no? I neglected to mention > in my post that the behavior goes away if I disable Firebug, btw. I > have disabled all other Add-ons. > > On Nov 14, 9:31 am, John J Barton <[EMAIL PROTECTED]> wrote: > > > Please post an example that does not use setTimeout(). > > > On Nov 14, 4:48 am, Jordan Brough <[EMAIL PROTECTED]> wrote: > > > > Firebug seems to be causing out of order execution on the first call > > > to eval on my Mac. > > > > I am running FireFox 3.0.4 on Mac OS X 10.5.5 on a a white 2.16GHz > > > Core 2 Duo iMac. I am seeing this behavior with both Firebug 1.2.1 > > > and Firebug 1.3X.0b3. I am not seeing the same behavior in Firefox/ > > > Windows (via Parallels). > > > > It seems that when Firebug is running, the first call to eval is often > > > 'put on hold', and execution of other code is allowed to proceed. > > > > Perhaps this is a 'feature' of JavaScript and/or Firefox that I don't > > > know about and is just exacerbated by Firebug...? > > > > I have posted a sample page which reproduces the problem most of the > > > time (hit refresh several times if it doesn't show up at first). > > > > The output of this code should have identical numbers being adjacent. > > > That is, something like this: > > > > 1,1,2,2,3,3,4,4,5,5,6,6,7,7,8,8,9,9,10,10, > > > > However, when Firebug is installed, more often than not I get this: > > > > 1,2,2,3,3,4,4,5,5,6,6,7,7,8,8,9,9,10,10,1, > > > > which means that the function containing the first call to eval must > > > have been put on hold while other code was allowed to execute, which > > > as far as I understand is not correct javascript behavior -- is that > > > correct? > > > > Steps to reproduce: > > > 1) Go tohttp://jordan.broughs.net/execution-order.html > > > 2) Enable all Firebug panels (Console, Script and Net) for the site. > > > 3) Keep reloading the page (cmd+r) until you see that the alert box > > > does not start with '1,1,' --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
