Menu
Community /Pin to ProfileBookmark
@NogDogOct 02.2019 — #Maybe the console updates the object as your code updates it? Pure speculation on my part, but wondering if that could be the case due to logging an object as opposed to some static string value or such? Maybe see if you get something different by converting it to JSON:
@daveyerwinOct 02.2019 — #@robbev#1609508
try this ...
<script>
let foo = {}
for(i=0;i<5;++i){
console.log(foo);
foo.bar = 'strange'+i;}
</script>
</script>
logs {}
bar: "strange4"
five times
so in firefox for each iteration of the loop
a reference to the object foo is stored for display in the console
javascript doesn't give up its control over the output to screen
until the loop is finished so
by the time console begins to print the object foo references
the property bar = 4
because console has stored a reference to foo and not a clone of foos state
console displays bar=4 five times
this logs the count down because
setTimeout breaks the javascript execution and
so allows the console to print the reference before
it is updated
Java object not populated chronologically
Hi all, I’m building an app using a javascript framework and for days I’ve been scratching my head over some very strange behaviour. After searching for hours I think it boils down to this: when I initiate a new object, use it and populate it afterwards, this doesn’t seem to happen chronologically. When I execute this code, the object I can see in my console already has the field ‘foo’, even though it’s added afterwards. How can this happen?
`let foo = {}
console.log(foo)
foo.bar = “strange”
`
Thanks in advance!
Sign in
to post a comment3 Comments(s) ↴
0
@NogDogOct 02.2019 — #Maybe the console updates the object as your code updates it? Pure speculation on my part, but wondering if that could be the case due to logging an object as opposed to some static string value or such? Maybe see if you get something different by converting it to JSON:<i>
</i>console.log(JSON.stringify(foo, null, 2))
0
@daveyerwinOct 02.2019 — #try this ...
<script>
let foo = {}
for(i=0;i<5;++i){
console.log(foo);
foo.bar = 'strange'+i;}
</script>
</script>
logs {}
bar: "strange4"
five times
so in firefox for each iteration of the loop
a reference to the object foo is stored for display in the console
javascript doesn't give up its control over the output to screen
until the loop is finished so
by the time console begins to print the object foo references
the property bar = 4
because console has stored a reference to foo and not a clone of foos state
console displays bar=4 five times
``<i>
</i><script>
let foo = {};
(function repeat(count){
console.log(foo);
foo.bar = 'strange'+count;
if(count)
setTimeout(function(){var c = count;repeat(--c + 1)},0);
}(4))
</script><i>
</i>``this logs the count down because
setTimeout breaks the javascript execution and
so allows the console to print the reference before
it is updated