maildev@lists.thunderbird.net

Thunderbird email developers

View all threads

Re: [Maildev] Buggy add-ons causing malfunctions of Thunderbird - Policy to disable them, do we have one, do we need one?

BB
Ben Bucksch
Sat, Dec 1, 2018 7:54 PM

Hey Jörg,

Jörg Knobloch wrote on 01.12.18 19:09:

I'd like to know whether we have or should have a policy to disable
buggy add-ons causing malfunctions of Thunderbird. Mozilla's Add-on
policies don't mention anything about malfunctions[1].

I'd assume that this is implicit, either by common sense, or by some
"quality" rule, that the addon cannot break the host app.

FWIW, WebExtensions are designed to avoid that very problem. We should
make more efforts creating WebExtension APIs in TB that are sufficient
for TB addons to do what they need to do. Then, after, we can encourage
addon authors to move there. But the APIs need to exist first (that's
the part that Firefox got wrong).

I'm particularly concerned about a particular add-on which has caused
four bug reports so far:

https://bugzilla.mozilla.org/show_bug.cgi?id=1506961
https://bugzilla.mozilla.org/show_bug.cgi?id=1506719
https://bugzilla.mozilla.org/show_bug.cgi?id=1511488
https://bugzilla.mozilla.org/show_bug.cgi?id=1421249

I've personally informed the author on 1st of August 2018 about the
malfunction, but during the four months that have lapsed, the problem
hasn't been addressed. This makes Thunderbird look bad since the fault
is not in a function of the add-on but instead causes (seemingly
unrelated) malfunctions of Thunderbird.

Opinions welcome,

Disable it using the addon store. (Given that that the author doesn't
answer).

Or fix it, upload a new version, with maintainer super powers, and all
users will be automatically updated to the fixed version.

Ben

Hey Jörg, Jörg Knobloch wrote on 01.12.18 19:09: > I'd like to know whether we have or should have a policy to disable > buggy add-ons causing malfunctions of Thunderbird. Mozilla's Add-on > policies don't mention anything about malfunctions[1]. I'd assume that this is implicit, either by common sense, or by some "quality" rule, that the addon cannot break the host app. FWIW, WebExtensions are designed to avoid that very problem. We should make more efforts creating WebExtension APIs in TB that are sufficient for TB addons to do what they need to do. Then, after, we can encourage addon authors to move there. But the APIs need to exist first (that's the part that Firefox got wrong). > I'm particularly concerned about a particular add-on which has caused > four bug reports so far: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1506961 > https://bugzilla.mozilla.org/show_bug.cgi?id=1506719 > https://bugzilla.mozilla.org/show_bug.cgi?id=1511488 > https://bugzilla.mozilla.org/show_bug.cgi?id=1421249 > > I've personally informed the author on 1st of August 2018 about the > malfunction, but during the four months that have lapsed, the problem > hasn't been addressed. This makes Thunderbird look bad since the fault > is not in a function of the add-on but instead causes (seemingly > unrelated) malfunctions of Thunderbird. > > Opinions welcome, Disable it using the addon store. (Given that that the author doesn't answer). Or fix it, upload a new version, with maintainer super powers, and all users will be automatically updated to the fixed version. Ben