Add-ons Update – Week of 2016/06/01

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

The Review Queues

In the past 3 weeks, 1277 listed add-ons were reviewed:

  • 1192 (93%) were reviewed in fewer than 5 days.
  • 68 (5%) were reviewed between 5 and 10 days.
  • 17 (1%) were reviewed after more than 10 days.

There are 67 listed add-ons awaiting review.

You can read about the recent improvements in the review queues here.

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.

Firefox 48 Compatibility

The compatibility blog post for Firefox 48 is up. The bulk validation should be run in the coming weeks.

As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition to make sure that they continue to work correctly. End users can install the Add-on Compatibility Reporter to identify and report any add-ons that aren’t working anymore.

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:

7 responses

  1. Charles wrote on :

    “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.”

    There are some bug about this specific point? I couldn’t find one.

    1. Jorge Villalobos wrote on :

      I don’t think this is being tracked on any bugs, but I believe the MDN article is wrong. I’ll confirm to have it corrected.

  2. A Firefox user wrote on :

    I’ve been a happy user of NoSquint for years; now it no longer works. I like the ability to change website background color to something easy on the eyes, along with text size.

    Please consider making it possible to use NoSquint again.

  3. BP wrote on :


    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.

    If you can comment, it would be most welcome.



    1. Jorge Villalobos wrote on :

      Every update they’ve submitted for their listing in the last year has been approved. There are no recent versions pending review or rejected by us.

      1. BP wrote on :


        So the developer versions, starting with version 4 back in January, haven’t been submitted for review, they’ve just been submitted for testing? Or…?

        LastPass have it stated on their support site that any incongruities between the versions on their website / the Chrome store and Firefox’s extensions site are due to Mozilla’s review process.

        Just trying to figure out why there is this disconnect.



        1. Jorge Villalobos wrote on :

          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.