Future updates beyond TB70
-
- Posts: 143
- Joined: February 18th, 2012, 8:41 am
Future updates beyond TB70
Recent 'big' updates of TB eg TB 60 & TB 68 appear to have included big internal changes to TB which have in many cases 'broken' much used add-ons. I understand TB70 will also make some big changes. Is this update also likely to break many addons ? Surely this repeated 'breaking' of add-ons is diverting volunteers time away from fixing TB itself back to fixing their add-ons..
-
- Posts: 6432
- Joined: February 3rd, 2009, 6:29 pm
Re: Future updates beyond TB70
Support for legacy addons to be dropped
http://forums.mozillazine.org/viewtopic ... &t=3055397
When tanstaafl says legacy addon in the above thread, he means a Thunderbird 68 compatible WebExtension using a manifest.json file with the legacy property. Addons in Thunderbird 60 use an install.rdf file. These addons are not WebExtensions.
About Thunderbird Addons
http://developer.thunderbird.net/add-ons/about-add-ons
Thunderbird WebExtension APIs
http://thunderbird-webextensions.readthedocs.io/
http://thunderbird-webextensions.readth ... egacy.html
I read that a legacy bootstrap addon should be fairly easy to convert to an experiment_apis addon.
Thunderbird 78 Roadmap (coming in summer 2020)
http://lists.thunderbird.net/pipermail/ ... 02024.html
http://forums.mozillazine.org/viewtopic ... &t=3055397
When tanstaafl says legacy addon in the above thread, he means a Thunderbird 68 compatible WebExtension using a manifest.json file with the legacy property. Addons in Thunderbird 60 use an install.rdf file. These addons are not WebExtensions.
About Thunderbird Addons
http://developer.thunderbird.net/add-ons/about-add-ons
Thunderbird WebExtension APIs
http://thunderbird-webextensions.readthedocs.io/
http://thunderbird-webextensions.readth ... egacy.html
I read that a legacy bootstrap addon should be fairly easy to convert to an experiment_apis addon.
Thunderbird 78 Roadmap (coming in summer 2020)
http://lists.thunderbird.net/pipermail/ ... 02024.html