- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 2 Oct 2012 07:16:30 +0000 (UTC)
- To: Glenn Maynard <glenn@zewt.org>
- Cc: whatwg@whatwg.org
On Mon, 1 Oct 2012, Glenn Maynard wrote: > > > > Primary goals: > > + have the new page use a different event loop if possible (new process) > > + have the window of the new page not be able to reach the opener via > > a named window.open() or target="" > > > > As a result, I think these are also necessary features: > > ... > > + have the new page be in a new browsing context > > It doesn't seem like you need a new browsing context to achieve both of > the above. (Maybe it's easier to implement in today's multi-process > browsers, if you happen to be opening a new tab at the same time you > start a new process, but that seems like an implementation detail.) You need a new WindowProxy object, otherwise anything that had access to it before still has access, and thus can't be in a new event loop. Saying you need a new WindowProxy object is basically equivalent to saying you need a new browsing context. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 2 October 2012 07:17:02 UTC