Object.prototype.toString.call does not behave as expected

[courtnek]

Filing an issue to track the following behavior (tested with Phantom 1.6.0):

http://stackoverflow.com/questions/14218670/why-are-null-and-undefined-of-the-type-domwindow

phantomjs> Object.prototype.toString.call(undefined);
"[object DOMWindow]"

[sodabrew]

Test again with PhantomJS 1.9.2, since that is the current release.

[jeffrifwald]

I can confirm Object.prototype.toString.call on both null and undefined returns [object DOMWindow] on Phantom 1.9.2 on my system.

[courtnek]

Actually I tried 1.9.2 on linux and got the following:

phantomjs> Object.prototype.toString.call(null)
{}
phantomjs> Object.prototype.toString.call(undefined)
{}
phantomjs> Object.prototype.toString.call("string")
{}

[JamesMGreene]

@courtnek: Don't trust the REPL.

[courtnek]

Confirmed. Still present in 1.9.2

[kibin]

Any updates on this? I have this issue on 1.9.8

[LeMoussel]

On Windows 7, with PhantomJS 2.0.0 I haven't this issue

phantomjs> Object.prototype.toString.call(undefined);
"[object Undefined]"
phantomjs>

[vitallium]

REPL is known to be broken in 1.9.X version.

[kibin]

Hm, I’m using it with karma, which installs 1.9.X by default. Will try to switch to 2.0, thanks.

[vitallium]

Fixed in 2.0.