From File/Import, the only option available is "cookies". When importing on "first run", the wizard shows the homepage import option, but only shows a single choice: the Firefox default homepage. Then the next page says migration complete, and the summary shows only cookies as being imported.
By code inspection, the Opera profile migrator hard-codes Opera 6-specific file names. Chances are that Opera has renamed the files since then.
Does this fix all of the issues on all platforms? I'm pretty tempted to just remove the Opera profile migrator, at least until we can rewrite it in JS and properly test it fully.
(In reply to Gavin Sharp (use firstname.lastname@example.org for email) from comment #3) > Does this fix all of the issues on all platforms? I'm pretty tempted to just > remove the Opera profile migrator, at least until we can rewrite it in JS > and properly test it fully. Yes. Opera 11 uses same filename on all platform (Windows/MacOSX/Linux). Current code seems to be for Opera 6 per comment #1. Also, I agree that we remove opera migration until rewriting new JS based code. (although we need ini parser for js components...) Gavin, should I remove this migration?
Yeah, let's just kill it, and file a followup to re-implement if needed.
Created attachment 578981 [details] [diff] [review] fix kill opera migrator.
(In reply to Makoto Kato from comment #4) > (although we need ini parser for js components...) What's wrong with nsIINIParser?
Comment on attachment 578981 [details] [diff] [review] fix A couple of things you forgot to remove: - NS_OPERAPROFILEMIGRATOR_CID #define in nsBrowserCompsCID.h, and a reference to it in nsModule.cpp - importFromOpera strings in migration.dtd r=me with those addressed, thanks!