- From: Ian Hickson <ian@hixie.ch>
- Date: Mon, 23 Sep 2013 20:25:40 +0000 (UTC)
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- Cc: whatwg@lists.whatwg.org
On Mon, 19 Aug 2013, Boris Zbarsky wrote: > > What Gecko does is that there is a set of canonical prototypes (the DOM > ones, Object.prototype, Array.prototype, etc) per global. The effective > script origin of a global is mutable. The effect of changing the > effective script origin of a global on the prototypes associated with > that global is that nothing at all happens to them: they stay as the > same objects. > > Now what happens to actual objects and their proto chains when they go from > being same-effective-script-origin to not or back... I'm not actually sure. > Bobby Holley probably knows, though; I think this is basically the situation > he's talking about in > <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20701#c38>. Isn't the answer to this question basically the answer to this thread? This new ES5/ES6 stuff all goes over my head, to be honest. I can't wrap my head around the implications, especially in a multi-global (let alone multi-origin) environment. Is there any chance people who do understand this stuff can tell me what it should do? Ideally people from more than one browser vendor, since all the browsers disagree and I get really different answers when I speak 1:1 to individuals from various browser vendors. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 23 September 2013 20:26:05 UTC