Closed
Bug 875189
Opened 12 years ago
Closed 12 years ago
|domObject instanceof otherWin.Constructor| should work
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 870423
People
(Reporter: bholley, Unassigned)
Details
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
Reporter | ||
Comment 1•12 years ago
|
||
Oh, this is just bug 870423. /me facepalms
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
![]() |
||
Comment 2•12 years ago
|
||
Wait, why? There is no sandbox here...
![]() |
||
Comment 3•12 years ago
|
||
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.
Reporter | ||
Comment 4•12 years ago
|
||
(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.
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•