In a recent message on the tb planning list someone said, "You should replace the
install.rdf file with a WebExtensions style manifest.json file, which includes the key
"legacy" set to true."

Could something about this be added to the cook book page
https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57**please? Or maybe there needs to be
a new page - Addons_Guide 61 +?

On 16/07/2018 10:31, Graeme wrote:

Could something about this be added to the cook book page https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 please? Or maybe there needs to be a new page - Addons_Guide 61 +?

Yes, we'll start a new page once Geoff's work has landed (any hour now) and (some) legacy add-ons start working again (somewhat). TB 61 didn't happen and we'll see whether we can put a TB 62 beta together before TB 63 beta is due in September. So I'd call the page Add-ons_Guide_62.

The general idea for TB 68 ESR will be though to make add-ons restartless, although the replacement for restartless add-ons in TB 68 isn't yet clear, or to WebExtensions, where we still have to define the interface.

Further reading on restartless add-ons:
https://mail.mozilla.org/pipermail/firefox-dev/2018-June/006503.html
https://mail.mozilla.org/pipermail/firefox-dev/2018-June/006507.html
https://bugzilla.mozilla.org/show_bug.cgi?id=1413432#c7

If getting ready for TB 60 was tough, getting ready for TB 68 will be even tougher :-(

Jörg.

First draft: https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_62

Jörg.