The Add-on SDK is a software development kit that provides a set of tools and APIs for building, testing, and packaging Firefox add-ons.
This is a hotfix release that updates 1.13.
Obtain the SDK in your favorite compression format:
Then unpack the archive, open the addon-sdk-1.13.1/README.txt file, and follow its instructions.
Hotfix updates to 1.13
The 1.13.1 release is a hotfix release that replaces the 1.13 release. It includes the following extra fixes:
- bug 836318: reverted context menu items in sub-menus to display by default as they did in 1.12
- bug 832401: fixed an issue where certain combinations of add-ons could result in an extra separator in the context menu
- bug 834754: fixed a logged error from the selection module
- bug 836061: fixed simple-storage and other modules when run against Firefox 21
Major Changes Since 1.12
We've rewritten the context-menu module, bringing the code up to date and fixing a number of bugs, including:
- bug 769709
- bug 700733
- bug 714914
- bug 700733
- bug 721849
- bug 729843
- bug 748743
- bug 757802
- bug 784611
- bug 800965
- bug 824482
Translators key supported in package.json
The package.json now enables an add-on author to list the translators of an add-on, and these are translated into "translator" elements in the add-on's install manifest. Thanks to community contributor CIAvash for this.
Unique IDs for tabs Tabs now have a unique ID: bug 795645.
This feature was originally announced as being in the 1.13.1 release, but actually won't be available until the 1.14 release.
See the complete list of known issues and requests for enhancement. We've listed some of the issues you're most likely to encounter separately below.
Can't load content from "data" directory into an iframe. Reported on the forum: https://forums.mozilla.org/addons/viewtopic.php?f=27&t=11689 - it's not possible to load content from an HTML file in an add-on's data directory into an iframe.
"TypeError: window.tabs is undefined" when opening a tab, in some circumstances.
Use of the deprecated global
postMessage() function in a content script will give the error "ReferenceError: console is not defined".
console.log() calls from a script included in a panel's HTML (as in this example: https://builder.addons.mozilla.org/addon/1042246/latest/) don't work: nothing is logged, either to the terminal console or the web console.
Specified panel width ignored when Firefox is maximized.
Access to Full Screen API blocked from context-menu API.
passwords.search() function "crashes" with some profiles.
If you change location in a content script using:
Nothing happens, instead, `location` attribute is just replaced by a string.
The tab array is not reordered to match the on-screen order of the tabs after a tab move event takes place.
The SDK will give an error if your package name contains spaces or Unicode characters.
If your add-on stores data using the simple-storage API, the data is not cleaned up when your add-on is uninstalled.
If an add-on is uninstalled while it's disabled, it's not notified of uninstall. If the add-on needs to do some special cleanup on uninstall, like removing persistent storage such as a file, this won't be possible if it has been disabled.
By default, widgets are placed on the add-on bar, and given a height to match the height of that bar. If the user moves the widget to a different toolbar, and that toolbar has a different height, the widget's height is not updated accordingly.
A widget containing HTML content gets no icon in the Customize Toolbar Window.
When a user removes a widget from the toolbar its
detach event does not get sent.
Selection events for a page are not sent if the page did not fully load (for example, because the user stopped the page loading).
If you have copy of mozrunner installed on your system, the
cfx test command may not work correctly.
There is a workaround for this.