Importing Firefox settings into SeaMonkey

[barbaz]

How can data be imported from a Firefox profile (prefs, extensions, bookmarks, searchplugins,...) into SeaMonkey? I normally copy/paste Firefox profiles, but it doesn't look like that will work here. Using SeaMonkey 2.19b2 on Linux.

[therube]

(actually I don't know if there is an automatic migrate of date from FF to SeaMonkey?)

> prefs

no particularly easy way that i know of?
compare prefs.js from one to the other?
make the changes wanted from that?

keep sets of changes you normally set in user.js, then you could just copy that directly over.

> bookmarks

(& a bunch of other stuff) are stored in places.sqlite.
would think that you could copy places.sqlite over directly?
if not, then a /bookmarkbackups/*.json should be able to be imported.

> search

no idea.

> session restore

FF calls it sessionstore.js, we call it sessionstore.json.
copy the .js over & name it .json.

(backup first)

[barbaz]

Thanks, that mostly worked, though I did need to copy prefs.js and places.sqlite twice to get the data to transfer. There are a few issues however:
- The built-in DOM Inspector extension disappeared, how do I get it back?
- Since media.navigator.enabled and media.peerconnection.enabled don't exist in SeaMonkey, how can I completely disable getUserMedia and WebRTC?
- I can't move addon toolbar buttons to the bottom bar like in Fx, how do you do this?

(actually I don't know if there is an automatic migrate of date from FF to SeaMonkey?)

I don't think so, it offered to import from Thunderbird (which has never been used on that machine) but not from Fx. Maybe such a feature was added in a later SeaMonkey, or 2.19b2 just doesn't like Fx 17 ESR?

[therube]

> DOM

I believe ...

If it were already there, from times ago, it would be retained.
If it were not there, you would have to download it.

DOM Inspector
(It should work & install in SeaMonkey regardless of what AMO may say.)


> media.navigator.enabled and media.peerconnection.enabled

I see both in SeaMonkey (2.22a).


> addon toolbar buttons

SeaMonkey has a "Status Bar", like used to be in older FF's, until FF removed it replacing it with the "Add-on Bar", so in that respect there may be more, heh, if you want to call it that, functionality in FF compared to SeaMonkey.

[barbaz]

> DOM

DOMi came back after running 2.19 release and didn't disappear when switching back to 2.19b2, so that's fixed.

> media.navigator.enabled and media.peerconnection.enabled

I see both in SeaMonkey (2.22a).

Those prefs are not in 2.19b2 or 2.19 release, but WebRTC functionality is definitely there. So how do I disable it? Do I need an Aurora version?

> addon toolbar buttons

SeaMonkey has a "Component Bar", like used to be in older FF's, until FF removed it replacing it with the "Add-on Bar", so in that respect there may be more, heh, if you want to call it that, functionality in FF compared to SeaMonkey.

Then what extension are you using to get the ABP icon where it is in the screenshot in this post?

[therube]

> media.navigator.enabled and media.peerconnection.enabled

I see both in SeaMonkey (2.22a).

OK, so they are not in the current 2.20 release.
Don't know about Beta?



ABP.
That's an option in ABP itself to have the icon display in the "status bar".

SeaMonkey has a "Component Bar"

Oops. Didn't mean to say that.
Corrected (below & above):

SeaMonkey has a "Status Bar"

[barbaz]

Don't know about Beta?

Latest beta I can get is 2.20b3, so I doubt it. I'll check 2.21 as soon as it's in beta.

I'm not so concerned about navigator.mozGetUserMedia because I wrote an extension for Fx 17 that disables that function independently of the pref. It shouldn't be hard to add support for SeaMonkey. What additional functions would I need to block in order to achieve the same effect as media.peerconnection.enabled = false? Also, would it work to set those prefs to false in user.js even though they have no default values?

[therube]

It is possible that a Pref is not listed in about:config but can be set & be effectual.
Is is possible that a Pref is listed in about:config & can be set & but that back-end support isn't there so it ends up being ineffectual .

Whether something works or not, you just have to try.


> additional functions ... media.peerconnection.enabled

I don't even know what that Pref does much less what else what might be needed.
Might try irc://moznet/seamonkey & see if they have any thoughts.

[barbaz]

It is possible that a Pref is not listed in about:config but can be set & be effectual.
Is is possible that a Pref is listed in about:config & can be set & but that back-end support isn't there so it ends up being ineffectual .

Whether something works or not, you just have to try.

I know... but how do I check for enabled WebRTC support without making P2P connections through some random remote server?

> additional functions ... media.peerconnection.enabled

I don't even know what that Pref does much less what else what might be needed.

That pref just enables/disables WebRTC. If that really can't be controlled in SeaMonkey 2.19, the prefs are in 2.18b4 and I could use that until I find a better solution.

ETA: thanks for all your help, therube. 2.18b4 is working for me now short of porting a few Firefox extensions. I also looked at the source tarball of SM 2.19b2 (specifically, mozilla/dom/media/PeerConnection.js and mozilla/dom/base/Navigator.cpp) and it looks like the media.peerconnection.enabled pref is supported. A test would be nice to make sure, but I think we can say the issues here are resolved.