Yes, it may be a one-line change for active addon authors, but it seems to me many already do not bother to fix these trivial things as it seems old-style addons are on life-support anyway. So perfectly working addons (their feature-wise) are not working just due to syntax changes in JS or small changes like this one. Also, will creating prefs on the fly behave the same as using the old default prefs infrastructure (i.e. can you reset the pref to the default value)? I just don't understand what the general point is to remove some features only to have them open-coded by all addon authors again in various slightly different ways. (That's similar to XUL) ______________________________________________________________ > Od: Jörg Knobloch <jorgk@jorgk.com> > Komu: maildev@lists.thunderbird.net > Dátum: 02.11.2017 15:15 > Predmet: Re: [Maildev] Fwd: Re: Proposal to remove some preferences override > >On 02/11/2017 14:38, Ben Bucksch wrote: > > > >That will cause massive breakage. > > > >Will it? It affects add-ons that define preferences that way. Looking at the add-ons I wrote, there's one affected which can be fixed by creating the preference on the fly. > > > >I suggest we should keep this patch, for our build of Gecko. > >I don't understand that sentence. > >Jörg. >

Aceman wrote on 02.11.17 15:46: > I just don't understand what the general point is to remove some features only to have them open-coded by all addon authors again in various slightly different ways. (That's similar to XUL) ditto Ben