#MOZILLA THUNDERBIRD ADD ONS CODE#
#MOZILLA THUNDERBIRD ADD ONS WINDOWS#

If you use any of these, there are available as the same names underneath Ci.

A bunch of globals in the message composition window were removed: nsIMsgCompDeliverMode, nsIMsgCompSendFormat, nsIMsgCompConvertible, nsIMsgCompType, nsIMsgCompFormat, nsIAbPreferMailFormat, nsIPlaintextEditorMail, nsISupportsString, and mozISpellCheckingEngine.

With this query, you can see all the bugs related to de-xbl-ing Thunderbird, and see how the removal of each binding is handled. That means, that if you have a XBL=binding in your add-on that extends a binding that is removed, your binding will fail.

Starting in Thunderbird 63, all XBL-bindings will be removed from Thunderbird.

The old name keeps working for now, but you get a deprecation warning in the error console if you use the old name.

mailServices.js has been renamed to MailServices.jsm.

You will also be unable to use the `nsIStringBundleService` interface. Replacement: richlistbox ( example migration)

XUL elements listbox, listboxitem and listcell.

To do this, add the file to the key 'legacy' instead of the value true in the following way: If your add-on has options specified in install.rdf, you need to put this in the manifest.json also. (Note: In this changeset the are build variables, add-ons need to use fixed strings). To use this overlay loader, XUL overlay legacy extensions must replace install.rdf file with a WebExtensions style manifest.json file, which includes the key 'legacy' set to true. For elements with event handlers these event handlers may run when the element is added, and they may fail if they rely on content being set up by a script which now runs after the creation of the element. This may cause unexpected behavior if your script previously ran before elements were inserted. Warning: Scripts in overlays are now run after all elements have been inserted into the document. An inbuilt overlay loader will load XUL overlays for extensions but may cause graphical glitches or malfunctions. 'Legacy' XUL extensions with overlays are still 'somewhat' supported in Thunderbird 63 and beyond. Important: Bootstrapped legacy extensions continue to work without a manifest.json file and will in fact break if you add that file.

#MOZILLA THUNDERBIRD ADD ONS CODE#

The code to handle bootstrapped extension and install.rdf has been moved to comm-central in bug 1510097 and should be stable now.

Composition API, bug 1503423, in preparationР”В«ootstrapped/restartless extensions with an install.rdf manifest.

Folder tab (3-pane) API, bug 1499617, in preparation.

Toolbar buttons WebExtensions API, bug 1487008, TB 64+.

#MOZILLA THUNDERBIRD ADD ONS WINDOWS#

Tabs and Windows API, bug 1455471, TB 60 and TB 63+.

As documented on Thunderbird WebExtension APIs, the following WebExtension APIs are available in Thunderbird:

Help wanted!Р”Вetails: WebExtensions have a manifest.json. But being a pioneer can be exciting, too. There are not many WebExtensions for Thunderbird yet, so you're in new territory.

There is some documentation for the Thunderbird WebExtension APIs.Р”Р‡or any API that is not yet provided, WebExtension Experiments can be used. Some applicable Firefox APIs work in Thunderbird (just try it), other Firefox APIs do not work, and Thunderbird has a few Thunderbird-specific APIs added. However, the APIs are necessarily different between Thunderbird and Firefox. For a general introduction, see WebExtensions and What are WebExtensions. This is the same type of addon that Firefox currently uses. The following extension types are supported in from Thunderbird 63 and beyond: The goal is to have one single source of information.Р”В¬ontact: Check the newsgroup and our communication channels. Please do not add new information to this wiki, but get in contact with us and share what is missing and it will be added to the official guide.

Mozilla thunderbird add ons