If you’re an add-on developer and are looking for contribution opportunities, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.

Extension Signing

The wiki page on Extension Signing has information about the timeline, as well as responses to some frequently asked questions. The current plan is to remove the signing override preference in Firefox 48. This was pushed back because we don’t have the unbranded builds needed for add-on developers to test on Beta and Release.

Multiprocess Firefox

If your add-on isn’t compatible with multiprocess Firefox (e10s) yet, please read this guide. Note that in the future Firefox will only support extensions that explicitly state multiprocess compatibility, so make sure you set the right flag:

WebExtensions are compatible by default and don’t need any flags to be set.

7 responses

Jorge,
“Note that in the future Firefox will only support extensions that explicitly state multiprocess compatibility”

That is somewhat different of the saying in the multiprocessCompatible flag article in MDN:
“In some future release we will change the default to true, and after that point incompatible add-ons will have to explicitly declare that they are not compatible.”

Is there anything public you and/or Mozilla can disclose about the LastPass addon issue? Is it being held up due to some performance or security concerns? I understand that they do submit updates at a more frequent pace than many other developers, but 4.0 was first pushed in January and the last reviewed update was pushed nearly three months ago.

There was a month and a week between the last two pushed dev updates, more than enough time to review the addon unless there was an outstanding issue — I’m sure there is a very sound reason for not disclosing why it was not reviewed and pushed to stable and also why that reason was not publicly disclosed, but that leaves LastPass addon users in a precarious position: stay with an outdated, likely insecure version that has performance/compat issues with e10s, or update to an unreviewed version. I dislike installing unreviewed developer versions and dislike having to install them from outside (i.e. not from the Mozilla addons website) sources even more.

They have submitted versions in the 4.* branch as Beta versions, so you can find them in the Development Channel if you scroll to the bottom of the listing page. Those are the ones that are being distributed on their site, I think.