This article offers advice for add-on developers that want to update their extensions to work in Firefox 7. Fortunately, most of the changes are relatively minor in this release, and few add-ons should need significant changes to work in Firefox 7.
As always, you will need to recompile any binary components to make them compatible with Firefox 7.
XPCOM changes affecting compatibility
Most of the changes in this release are XPCOM interface removals, or removals of specific, obsolete APIs from interfaces.
The following interfaces are the ones that were removed that will most likely impact extension developers:
A few interfaces have methods that have been changed:
A number of non-standard methods have been removed from this interface. This affects the
File.getAsBinary()methods. However, this functionality can now be found in the standard
Other changes of note
These changes won't affect compatibility (we weren't kidding when we said there weren't many changes that do in this release), but do add capabilities that are easy to take advantage of that might be of special use to you.
Components.utils.load(). This can be particularly handy with restartless (boostrapped) extensions, so that you can unload an old version of a code module when a new version of your add-on is installed.
You can now have preference options inline in the Add-on Manager window, which lets users configure your add-on without having to open a separate preference dialog box. There are limits to what types of configuration controls can be provided, but this is still very helpful -- plus it works for restartless (boostrapped) extensions.