Are most of the existing add-ons being sacrificed due to adding support for WebExtension?

Eyal Rozenberg eyalroz at
Thu Nov 23 19:04:31 UTC 2017

I just want to remind people that in TB 57 we're seeing several changes 
which do not preclude (traditional) add-ons, but do cause bustage that 
needs addressing. See:
[Bug 1417209] Thunderbird 57.0b1 hangs before any windows come up with 
any of numerous add-ons

... and this has nothing to do with the switch to WebExtensions (as far 
as I can tell). Many users may conflate this temporary bustage with the 
WebExtensions issue - and this can add to their confusion. So definitely 
a +1 for reiterating plans, positions and decisions more publicly.


On 11/22/17 4:08 AM, Eric Moore wrote:
> "In general, there have been many interface/IDL changes over the 
> mozilla57/58/59 period and some changes to JS syntax that most add-ons 
> will require some sort of update to their code. That will distinguish 
> the "maintained" add-ons from the "unmaintained" add-ons some/most of 
> which will stop working.
> ....
> Jörg."
> Who made the decision to essentially kill off legacy add-ons and when 
> was it made?
> Who was aware of that decision?
> Why wasn't this treated as a strategic decision that needed 
> feedback/discussion like was done with getting a new home?
> A lot of what makes Thunderbird so popular is its large collection of 
> user developed add-ons. My impression is that many users have given up 
> due to poor doc., too frequent changes to interfaces, and uncertainty 
> about the direction of add-ons. Look at Paolo "Kaosmos" for example. A 
> cookbook on how to convert a legacy add-on and migrate to a new add-ons 
> web site isn't going to change that.
> What is the plan to deal with the bad publicity when web sites like 
> hear of this?
> _______________________________________________
> tb-planning mailing list
> tb-planning at

More information about the tb-planning mailing list