Robert O’Callahan posts some interesting issues with Chrome
Mozilla hacker Robert O’Callahan highlights some interesting issues concerning Chrome in this post…
– Multiple processes rendering to a single window on Mac. There’s no supported way to do that AFAIK. From your docs (great docs by the way!), it seems you don’t have an answer there yet either.
– Separate-process plugins rendering in windowless mode. I haven’t had a chance to grovel through your code yet, but I didn’t see anything in the docs about it. Sounds especially tricky in Chrome since, if I understand correctly, all interaction between the plugin and the page is routed through the master browser process.
– Synchronous two-way script interaction between the page and a separate-process plugin seems like it’s hard to make performant.
– Running different-origin iframes in separate processes sounds hard; the interaction between iframes and their hosts is complex and bears on Web compatibility. (And the interaction gets more complicated with HTML5 “seamless” iframes.) But it really has to be solved, I think, because otherwise a compromised renderer process can violate the iframe security boundary — a gaping hole in the security architecture.
Would be interesting to see how google answers these.
