52
edits
Changes
tb-war-on-xbl
* XUL <tt>stringbundleset</tt> / <tt>stringbundle</tt>. You will also be unable to use the `nsIStringBundleService` interface.<br/>Replacement: Use <tt>Services.strings.createBundle(...)</tt>.<br/>In order to use stringbundles, you need to load stringbundle.js in your XUL: <tt><script type="application/x-javascript" src="chrome://global/content/elements/stringbundle.js"/></tt>, but the XUL Overlay loader takes care of this. See also [https://bugzil.la/1459743 bug 1459743]
* <tt>mailServices.js</tt> has been renamed to <tt>MailServices.jsm</tt>. The old name keeps working for now, but you get a deprecation warning in the error console if you use the old name.
* Starting in Thunderbird 63, all XBL-bindings will be removed from Thunderbird. That means, that if you have a XBL=binding in your add-on that extends a binding that is removed, your binding will fail. With [https://bugzilla.mozilla.org/buglist.cgi?o1=equals&v1=1484976&f1=blocked this] query, you can see all the bugs related to de-xbl-ing Thunderbird, and see how the removal of each binding is handled.
== Removed in Thunderbird 64 ==
