Mozilla Add-ons Community Blog
Categories: compatibility developers documentation

Add-ons Update – Week of 2015/07/22

7 responses

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.

Add-ons Forum

As we announced before, there’s a new add-ons community forum for all topics related to AMO or add-ons in general. The Add-ons category is one of the most active in the community forum, so thank you all for your contributions! The old forum is still available in read-only mode.

The Review Queues

  • Most nominations for full review are taking less than 10 weeks to review.
  • 308 nominations in the queue awaiting review.
  • Most updates are being reviewed within 10 weeks.
  • 127 updates in the queue awaiting review.
  • Most preliminary reviews are being reviewed within 12 weeks.
  • 334 preliminary review submissions in the queue awaiting review.

The unlisted queues aren’t mentioned here, but they are empty for the most part. We’re in the process of getting more help to reduce queue length and waiting times for the listed queues.

If you’re an add-on developer and would like to see add-ons reviewed faster, 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 40 Compatibility

The Firefox 40 compatibility blog post is up. The automatic compatibility validation will be run soon.

As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition (formerly known as Aurora) 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

We announced that we will require extensions to be signed in order for them to continue to work in release and beta versions of Firefox. The wiki page on Extension Signing has information about the timeline, as well as responses to some frequently asked questions.

A recent update is that Firefox for Android will implement signing at the same time as Firefox for Desktop. This mostly means that we will run the automatic signing process for add-ons that support Firefox for Android on AMO, so they are all ready before it hits release.

Electrolysis

Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running content code in a different process than browser code. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.

We will be talking more about these changes in this blog in the future. For now we recommend you start looking at the available documentation.

7 comments on “Add-ons Update – Week of 2015/07/22”

  1. Jake wrote on

    It is very discouraging to see that the preliminary review process (which is suppose to be faster then the normal review process) is taking more time than the normal review process. It would be great if you guys could do a post about how the new upcoming system will improve this drastically (not just vague words, but actual expected goals), how the updates will be posted faster and why developers that gave up on Firefox because of the snail review process should return.

  2. farah wrote on

    hi
    firefox is my favorite browser, but right now , i do not understanding what happened with the firefox because oftentimes is Not responding, im install latest vesion and adobe flash palyer ,but just run 1 and 2 days to normally but after that back to Not Responding ,, give resolve please,,

    thanks

  3. ahli sumur jogjakarta wrote on

    hallo everybody, i just installed new mozilla firefox in friends laptop. I get some problem like this: some time mozilla give stop work and laptop hang. What the problem ? thanks

    1. ahli sumur jogjakarta wrote on

      sorry, before installed firefox I install IDM.

  4. lorezi wrote on

    Having just rolled back from the beta version after it disabled half my addons, I’m sad to say that if there’s no override come 42, i’m looking for a new browser.

    Many of my addons have been fussed with, either by me or by people I know, and seeing as they’re a derivative of an existing addon (in some cases one that is no longer supported), there’s no way they’re ever going to be signed. This is precisely why I stopped using chrome, despite the speed upgrade and overall functionality. In time all addons will stop being supported by their creators, and until the functionality breaks completely they’ll either chug along just fine, or be updated by fans who aren’t able to sign them.

    Echofon, ljlogin, new xkit, classic theme, and the addon bar are all required for what I do or have no replacement available. The first three are unsigned at the moment and are continuations/patches of the original addons. The other two are fixes for ui changes that firefox made, and I have no idea how long those are going to be supported- which is “great” since classic theme is linked in the firefox entry about the ui change itself.

    We are not children, we can install our own things. If you have to have a default setting that disables homebrew creativity, fine, but let us have a permanent setting in 42 that we can disable.

    or hey, introduce a signed addon that does it.

  5. Genevive Ocansey wrote on

    Hello everyone, It really hard to understand huge changes. I always use the firefox browser because it seems very easy to use. But now i faced a lot of problems while using firefox. Sometimes the add-ons remove automatically and often times the browser hangs.

    1. Jorge Villalobos wrote on

      Please visit our support site for help.