On Mon, Aug 24, 2009 at 10:08 AM, Jeremy Moskovich<jer...@chromium.org> wrote: > * Due to some technical limitations with the FF libraries, we need to load > them in a separate process. It also doesn't seem like a good idea to run > code out of an arbitrary library in the main process.
Coincidentally, I was just chatting with an Epiphany (WebKit+Gtk) developer about Firefox import and he too was lamenting how complicated it is to get this data out of Firefox. I had suggested a utility process might be the best way. (Note: not a complaint about Firefox; it's likely it's even harder to import this sort of data out of us...) > * The first run dialog needs to be displayed very early on in the launch > process since we need to display it before enabling stats and crash > reporting so we can ask for the user's consent. The dialog is brought up > before we've fully initialized Cocoa which is concerning in terms of it's > interaction with the main app runloop, There are also UI artifacts - > http://crbug.com/19643 As far as I know there are no such issues on Linux, so we don't have anybody working on doing this split. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
