W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

Re: New full Unicode for ES6 idea

From: Brendan Eich <brendan@mozilla.org>
Date: Sun, 19 Feb 2012 15:11:38 -0800
Message-ID: <4F4181AA.1010008@mozilla.org>
To: "Mark S. Miller" <erights@google.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>, mranney@voxer.com, es-discuss <es-discuss@mozilla.org>
Brendan Eich wrote:
> Mark S. Miller wrote:
>> On Sun, Feb 19, 2012 at 12:33 AM, Brendan Eich <brendan@mozilla.com 
>> <mailto:brendan@mozilla.com>> wrote:
>> [...]
>>
>>     Why the global object? Because for many VMs, each global has its
>>     own heap or sub-heap ("compartment"), and all references outside
>>     that heap are to local proxies that copy from, or in the case of
>>     immutable data, reference the remote heap.
>> [...]
>>
>> Is this true for same origin iframes? I have always assumed that 
>> mixing heaps between same origin iframes results in unmediated direct 
>> object-to-object access. If these are already mediated, what was the 
>> issue that drove us to that?
>
> Not all engines mediate cross-same-origin-window accesses.

Sorry, I misused "mediate" incorrectly here to mean heap/compartment 
isolation. All engines in browsers that conform to HTML5 must mediate 
cross-frame Window (global object) accesses via WindowProxy, as 
discussed in other followups.

> I hear IE9+ may, indeed rumor is it remotes to another process 
> sometimes (breaking run-to-completion a bit; something we should 
> explore breaking in the future for window=vat).

(Hope that parenthetical aside has you charged up -- we need a fresh 
thread on that topic, though... ;-)

/be
Received on Sunday, 19 February 2012 23:12:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC