the_unlettered_tellurian

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.

My last post for the day… please start Flocking. Meaning, please start using this really cool new browser that goes by the name “Flock”.

The tagline for the browser is “The Social Web Browser” and its got a whole bunch of features that will be of great help if you are the kind who uses quite a bit of so called web 2.0 features available on sites.

I haven’t used all the available features, but it looks promising, and yes, it is definitely fast.

Flock is powered by the Mozilla engine, and is currently in Beta 2. Yep, still in beta so be careful while using it, although it hasn’t crashed once in the last couple of months I have been using it.

Snapshot of features in Flock 2 Beta can be found here.

I heard even Stumbleupon works with it now, although I haven’t installed the extension yet.