Add-ons Update – Week of 2012/09/26

Jorge Villalobos

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 2 weeks to review.
  • Most updates are being reviewed within 10 days.
  • Most preliminary reviews are being reviewed within 1 week.

These stats are taken from the last queue report:

  • 102 nominations in the queue awaiting review.
  • 78 updates in the queue awaiting review.
  • 77 preliminary review submissions in the queue awaiting review.

If you want the review queues to shorten, you can help! If you’re an add-on developer, please consider joining our team. Visit our wiki page for more information.

Add-on Policies

In order to make it clearer to everyone what we expect from add-on behavior, we published our current draft of the Add-on Guidelines. We haven’t set them up in their permanent location yet, but they are already being enforced, so don’t hesitate to measure up your add-ons against them. Also, don’t hesitate to report any guideline violations you encounter.

I also published an update about our add-on installation policies, which are already part of the Add-on Guidelines. We’re contacting all developers who are not following these policies so that they are aware of them.

Firefox 16 Compatibility

The Firefox 16 compatibility blog post and compatibility bump are coming soon.

Major change coming up in Firefox 17

The landing of bug 553102 made major change that can break compatibility for many add-ons. In a nutshell, if you set expando properties in JS objects in the content that point to chrome objects, you need to explicitly add the properties to the __exposedProps__ list of that object. A deprecation warning was added in Firefox 15. There’s more information here.