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 10 days to review.
- Most updates are being reviewed within 1 week.
- Most preliminary reviews are being reviewed within 10 days.
These stats are taken from the last queue report:
- 52 nominations in the queue awaiting review.
- 52 updates in the queue awaiting review.
- 58 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.
Test Your Add-ons for Memory Leaks!
There is an ongoing effort to track and stomp memory leaks in add-ons. Here’s where you can help, either by testing the add-ons you created, or testing the add-ons you use. Please read the article on Zombie Compartments, particularly the add-ons section. It should give you some pointers on how to find leaks and how to avoid them. The short version is: don’t hold any references to DOM objects after the document is closed.
With the resolution of bug 695480, whole classes of compartment leaks have been resolved on the Firefox side. This means that even if an add-on holds on to DOM references when it shouldn’t, they will be properly claimed. But this doesn’t mean that you shouldn’t test and fix your code! This fix will be introduced in Firefox 15.
Firefox 14 and 15 Compatibility
The Firefox 14 compatibility blog post is up, and the compatibility bump to 14 happened shortly after. Firefox 15 compatibility docs are coming up 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 (to be released soon), so you can test your add-on on Firefox Beta and see if the warning shows up in the console for you. If it does, you should update your code as soon as possible. Old versions of the Add-ons SDK are also affected, so all SDK add-ons should be updated to the latest stable version.