875189 - |domObject instanceof otherWin.Constructor| should work

Status: RESOLVED DUPLICATE of bug 870423

Description

[Bobby Holley (:bholley) (busy with Stylo)]

So, [1] alerts true, and [2] alerts false. Heycam says that he updated the spec in [3] so that instanceof should be scope-agnostic. This is kind of unexpected, since I'd imagine that these two cases would look the same under the hood: we should end up in the compartment of the constructor, with the object being a cross-compartment wrapper. 

[1] http://bit.ly/14Tde2J
[2] http://bit.ly/12XLbxI
[3] http://dev.w3.org/2006/webapi/WebIDL/#es-interface-hasinstance

Comment 1

[Bobby Holley (:bholley) (busy with Stylo)]

Oh, this is just bug 870423. /me facepalms

Comment 2

[Boris Zbarsky [:bz] (still digging out from vacation mail)]

Wait, why?  There is no sandbox here...

Comment 3

[Boris Zbarsky [:bz] (still digging out from vacation mail)]

Oh, I see.  The key is having the RHS be a proxy of any kind.... I guess we tested it for cases when the _LHS_ was the proxy, but not the other.  Funtimes.

Comment 4

[Bobby Holley (:bholley) (busy with Stylo)]

(In reply to Boris Zbarsky (:bz) from comment #3)
> Oh, I see.  The key is having the RHS be a proxy of any kind

Well, a function proxy.