Changes

__TOC__ The picture following extension types are supported in from Thunderbird 63 and beyond : === WebExtensions ===WebExtensions with a manifest.json. The following WebExtension APIs are available in Thunderbird version :* Tabs and Windows API, {{bug|1455471}}, TB 60 and TB 63+* Address Book API, {{bug|1469238}}, TB 60 is rather uncertainand TB 63+* FileLink API, {{bug|1481052}}, TB 64+, given the continued high rate of change will be in Firefox platform codeTB 60. We will work with add4* Toolbar buttons WebExtensions API, {{bug|1487008}}, TB 64+* Folder tab (3-on authors pane) API, {{bug|1499617}}, in preparation* Composition API, {{bug|1503423}}, in the coming months to determine a viable postpreparation* And more, check meta-60 add-on strategy. Below are some general thoughts, which if you have programming questions or wish to discuss the future {{bug|1396172}}WebExtension Experiments can be posted in the mozillaused for any API that is not yet provided.devYou can read more information at https://github.apps.thunderbird newsgroup, see [[Thunderbirdcom/thundernest/tb-web-ext-experiments/CommunicationChannels#If_you.27re_a_developer|Communication Channels]].

Work === Bootstrapped extensions ===Bootstrapped/restartless extensions with an install.rdf manifest. The code to handle bootstrapped extension and install.rdf has been undertaken moved to keep supporting legacy addcomm-ons "somewhat" in Thunderbird 63 and beyond. We implemented an overlay loader that will load XUL overlays for add-ons but may cause graphical glitches or malfunctions. We're tracking this central in {{bug|14762591510097}}and should be stable now. Important: Bootstrapped legacy extensions continue to work without a manifest.json file and will in fact break if you add that file.

To use this overlay loader, === "Legacy" XUL extensions with overlays ==="Legacy" XUL overlay legacy add-ons must replace install.rdf file extensions with a WebExtensions style manifest.json file, which includes the key overlays are still "legacysomewhat" set to truesupported in Thunderbird 63 and beyond. See Lightning as an example:<br />https://hgAn inbuilt overlay loader will load XUL overlays for extensions but may cause graphical glitches or malfunctions.mozilla.org/comm-central/rev/e81f4b59a00a7d3e18d50fd3851ecbd47762a186#l2.5 <small>(Note: In We're tracking this changeset the @variables@ are build variables, add-ons need to use fixed strings)</small>.<br />Important: Bootstrapped legacy add-ons continue to work without a manifest.json file and will in fact break if you add that file{{bug|1476259}}.

Add-on authors who want to make their add-ons compatible with Thunderbird version from 63 and beyond to version 68 ESR have three options:* Rely on the mentioned To use this overlay loader, XUL overlay loaderlegacy extensions must replace install. This is only rdf file with a short-term stopgap solutionWebExtensions style manifest.* Make their add-ons restartlessjson file, although which includes the replacement for restartless add-ons in TB 68 isn't yet clearkey "legacy" set to true. Further reading on restartless add-ons:** httpsSee Lightning as an example:<br //mail.mozilla.org/pipermail/firefox-dev/2018-June/006503.html** >https://mailhg.mozilla.org/pipermail/firefoxcomm-devcentral/2018-Junerev/006507e81f4b59a00a7d3e18d50fd3851ecbd47762a186#l2.html** https5 <small>(Note://bugzilla.mozilla.org/show_bug.cgi?id=1413432#c7* Convert their In this changeset the @variables@ are build variables, add-on ons need to a WebExtension, using WebExtension Experiments for any API that is not yet provided. This is the preferred approach. You can read more information at https:use fixed strings)<//githubsmall>.com/thundernest/tb-web-ext-experiments/<br><p/>