Re: Objects in console.log not synchronous
143 views
Skip to first unread message
Jan Honza Odvarko
Aug 20, 2012, 2:20:39 AM8/20/12
to Firebug
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 <mgas...@gmail.com> 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?
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 <mgas...@gmail.com> 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?
Reply all
Reply to author
Forward
0 new messages