Firebug doesn't perform deep copy of logged objects. The log stores only a reference to it to get the info when it's rendered - which can happen asynchronously, yes.
Logging itself is asynchronous to avoid UI freeze in case there is big amount of logs. Honza On Aug 19, 4:03 pm, Martijn Gasman <[email protected]> wrote: > I'v read about this on stackoverflow before, and when I console.log the > root of an Object, it will not print the current state of the object, just > the latest state, so when that Object has changed or has a differnt. Only > when I console.log a Object.attr it will be the right one. > > I can't be the only one who noticed? -- 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
