After digging into the problem I have found that if a JS object
defined on a page eg:
var a = {a:1, b:2, next:3};
... is accessed from chrome using wrappedJSObject, the "next" property
is not visible when iterating properties using
for-in loop.
Is this known problem?
Honza
No. Please file?
-Boris