15/25 because I didn’t read the directions
17/25 after I did
25/25 after I used the WebKit console, 😛

You got 24/25 correct. Incorrect: #25 Why did I answer “foo” instead of “f,o,o”? Hm…

P.S.: first I had

You got 22/25 correct. Incorrect: #10, #23, #25

because didn’t read disclamer carefully and wrote SyntaxError instead of ERROR. So, I think I answer #10, #23 correctly.

Dmitry.

#3: I can’t freakin’ believe I got this one wrong! Totally my fault.
#6: This one is debatable IMHO. I can’t wait to read the rationale behind it.
#10: This one is a valid expression, but not a valid statement; I answered with the result of {a: 1, b: 2}[["b"]] as an expression (2) so either the question was not exceedingly clear, or… oh well, after failing #3 I’m not sure of anything any longer.
#12: This one is a valid statement, resulting in 2, but also a valid Object literal… oh wait, there’s no such thing as an Object literal in the standard (plus eval‘ing #12 yields 2 as well) so… my fault, again.
#23: I wrote “SybtaxError” as an answer. LOL! That makes #23 my 21st correct answer, typos apart, I suppose.

Damian (and qFox) seems to have covered all of the answers! Thanks.

you can completely ignore it and focus on [0]. E.g. [0].toString() gives “0″. James actually has taken “[0]” as a correct answer probably suggested by the returned value in Firebug. But IMHO it should be “0″.

Why? [0] returns [0] … why do we need to toString() it?

You got 8/25 correct.

Thanks for all

My result sucks =X