On 9/25/13 3:47 PM, Mark S. Miller wrote:
Hi Boris, I don't understand what you mean by "in general". I think the
SpiderMonkey use of cross-realm membranes is a great use case for
membranes, and I don't understand why they need any special logic at all
-- beyond the logic expressed by their handlers, which must include
revocation.
Mark,
The issue is that if I have access to a different-realm Location object
called "loc", say, then:
Object.getOwnPropertyDescriptor(Location.prototype, "href").get.call(loc)
should throw if the "loc" is not same-origin with me. But:
Object.getOwnPropertyDescriptor(Location.prototype,
"href").set.call(loc, "whatever")
should perform the set. (There are actually some more complications
here for the specific case of Location, but let's ignore them for now.)
What that means in practice is that the membrane isn't actually
"revoked": it needs to be unwrapped to the real underlying object in
some cases, but not others.
The way we implement that, again, is with a way to unconditionally
unwrap a cross-realm membrane, and a way to ask a cross-realm membrane
whether it's ok to unwrap it. Some of the methods/getters/setters
involved use the former, and some use the latter.
Note that in this case the actual property getter/setter is gotten
without any interaction with membranes at all. The only question is
when a membrane around the thisArg to a function can be pierced to get
to the thing the function actually knows how to operate on.
-Boris
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
