707601 - Rewrite Opera profile migration in js

Status: RESOLVED DUPLICATE of bug 1284106

(Firefox :: Migration, defect)

Description

[Makoto Kato [:m_kato]]

+++ This bug was initially created as a clone of Bug #539133 +++

Opera profile migration doesn't work well because current code seems to be for Opera 6.

- reimplemented by JS (we may require ini parser by js)
- use async as possible for performance and chromehang
- test harness like bug 706017

Comment 1

[:Gavin Sharp [email: [e-mail]]]

(In reply to Makoto Kato from comment #0)
> - reimplemented by JS (we may require ini parser by js)

We have nsIINIParser, FWIW.

Comment 4

[antistress]

maybe this bug depends on  Bug #718608 ?

Comment 5

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

yes

Comment 7

[:Gavin Sharp [email: [e-mail]]]

Makoto Kato, I assume you aren't working on this?

I wonder whether we should WONTFIX. I suppose some Opera users may be abandoning it soon given their recent announcement, but I'm not sure this is worth the effort even still.

Comment 9

[MAWA VANSMOOKEY]

Attachment: photoe

good

Comment 10

[Matthew N. [:MattN]]

Opera is based on Chromium now so we would subclass the Chromium migrator if we wanted Opera import support (bug 1284106)