Realm, schmealm!

Brendan Eich brendan at
Thu Aug 1 13:33:48 PDT 2013

Ian Hickson wrote:
> On Thu, 1 Aug 2013, Brendan Eich wrote:
>>> That actually gets you closer to what the spec says (closer to the
>>> legacy model) than the Gecko approach,
>> How so? Can you give an example where Gecko doesn't do what the spec
>> says?
> The difference between the model I described and the Gecko model is that
> the isolation is amongst groups of similar-origin browsing contexts, so
> document.domain doesn't cause a problem. That is, two sibling iframes at
> and would be in
> the same process, not isolated from each other. It's essentially the model
> described in the spec, implemented with Gecko-style defense-in-depth.

So object refs not linked through window or document do get revoked on 
domain change, or do not?

>> How about the non-enumerable thing? That doesn't really protect anything
>> in ES5 era, and as Allen says it doesn't protect against guessed-name
>> probing.
> I'm not sure what this refers to. Can you elaborate?

When theincumbent script 
script origin 
different than a|Window|object's|Document| 
script origin 
the user agent must act as if any changes to that|Window 
properties, getters, setters, etc, were not present, and as if all the 
properties of that|Window 
had their [[Enumerable]] attribute set to false.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list