Re: RFC: Electrolysis manifesto: Chrome never blocks on content

On 4/23/10 3:47 PM, Chris Jones wrote:
> OK. Modulo the bug with 'rpc' and ctors not playing well together, I
> think window.open (is this createWindow() in PIFrameEmbedding?)

Yes.

> can be 'sync'. I'm working on fixing this bug right now.

But sync means the content process can't be reentered, no?  In 
particular, within the createWindow call we currently run 
nsFrameLoader::ReallyStartLoadingInternal, which seems to send several 
messages to the child process.  Or are those all async except the ctor 
and therefore ok within a sync call?

> No thanks :). I think 'sync'++ is the right choice here.

If we can make it work, I agree.

-Boris