-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test/fix interoperability with SeaMonkey #29
Comments
Should work with SeaMonkey without use of the Extension Converter |
If you add seamonkey to the package.json "engines" list, it runs and the addon settings window in seamonkey shows it installed. Here's a diff:
But no button appears. I'm guessing it has something to do with instantiation of a component not available in seamonkey. Not sure which one. Here's some debug output.
|
I was able to get the plugin to install by making a more traditional installer, using chrome and xul. In order to make our javascript compatible with SeaMonkey, you need to change all of the component acronyms to their full names because they do not exist in SeaMonkey(ie. Cc -> Component.Classes). However, our Firefox plugin uses some jpm modules that have not been implemented in SeaMonkey, most notably PageWorkers. In order to make the plugin fully functional, you will need to track down how each of these is implemented in Firefox and then reverse engineer them for SeaMonkey. |
From a user, posted in mozilla.dev.security.policy: I downloaded Certificate Manager 1.0.2, used the Extension Converter for SeaMonkey at http://addonconverter.fotokraina.com/ in an attempt to make it compatible with SeaMonkey, and installed in SeaMonkey 2.39 on Windows 7. I did not get the icon you describe.
The text was updated successfully, but these errors were encountered: