Mozilla Add-ons Community Blog
Categories: compatibility developers documentation

Add-ons Update – Week of 2014/12/24

4 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.

The Review Queues

  • Most nominations for full review are taking less than 9 weeks to review.
  • 42 nominations in the queue awaiting review.
  • Most updates are being reviewed within 6 weeks.
  • 33 updates in the queue awaiting review.
  • Most preliminary reviews are being reviewed within 6 weeks.
  • 63 preliminary review submissions in the queue awaiting review.

Thanks to our volunteer reviewers, most new submissions are being handled within a day or so (the measurements above are based on the state of the queue and not the actual waiting times). We still have a large backlog of complex add-ons that require admin review, but we’re making progress in decreasing it.

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 35 Compatibility

The Firefox 35 compatibility blog post is up. The automatic AMO validation was also run already.

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.

Firefox 36 Compatibility

Coming up.

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 each content tab in a different one. 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 near future. For now we recommend you start looking at the available documentation.

Happy holidays to those who celebrate them 🙂

4 comments on “Add-ons Update – Week of 2014/12/24”

  1. Vinayak Agrawal wrote on

    Hey, I am facing issue in ‘cfx test’ that it always gets failed.
    Even if I create a sample addon using ‘cfx init’ and then test it using ‘cfx test’, it gives error.
    Others are also facing this, here is a link I found on SO: http://stackoverflow.com/questions/27652770/cfx-test-fails-after-setting-up-firefox-add-on-environment

  2. Arthur wrote on

    I’m currently running about 500 tabs – NOT a joke – does that mean I will have 500 threads running ? Also, does anyone ever test something like that XD

    1. Jorge Villalobos wrote on

      Different processes, not threads, as I understand it. Also, it would depend on whether you have all 500 tabs loaded, since Firefox only loads that tabs you click on after a restart. There are various Mozillians who use quite a lot of tabs (I hover around 30, which is probably mid-range), so I bet those cases are being looked at. What I do know about multi-process browsers is that they tend to use more memory that single-process ones, so 500 running tabs would probably make a noticeable difference in memory consumption (I’m sure they already do).

      1. wbamberg wrote on

        As far as I know, in the first iteration of multiprocess Firefox, all content tabs will live in the same process. So there will be just two processes, one for chrome and one for content. In future iterations there might be more than one content process, and I’m sure cases like this will be looked at.