Hi Charles, first question: Which Firebug, Firefox and OS version? second question: Do you have a test case so we can reproduce this? third question: Did you already step through your code using the debugger<http://getfirebug.com/wiki/index.php/Script_Panel>to check what is happening?
Sebastian On Friday, March 16, 2012 8:02:08 PM UTC+1, Charles wrote: > > I have written a piece of code that is heavily iterative. In a main > function that is called in one of the loops, I declare a new blank > array which is immediately followed by a console.log() statement for > the new variable. The first few times through the loop the variable > shows as null (as should be since it has just been declared). > However, after running though a few times, the console.log() statement > starts yielding variables with values as if the console.log() > statement were further down in the code (the console shows it > containing values that it should not yet contain). Has anybody else > had similar issues before? Is it possible that the console is > reacting too slowly to catch the variable in its recently initiated > state? I'm dumbfounded with this problem. Strange that the > console.log() works correctly the first few times through but after > that, things get weird. -- 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 https://groups.google.com/forum/#!forum/firebug
