<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 02-Dec-18 4:39 AM, Jörg Knobloch
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:6dda722d-38b0-9f8b-5f89-1ce565de5293@jorgk.com">Hello
estimated members of the Thunderbird community,
<br>
<br>
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]. <br>
</blockquote>
<br>
I think it is implicit that an add-on does not cause the host
program to fail. But disabling is a very problematical issue. <br>
See <a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1359469">https://bugzilla.mozilla.org/show_bug.cgi?id=1359469</a> and
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1354912">https://bugzilla.mozilla.org/show_bug.cgi?id=1354912</a> for the
trouble blocking McAfees anti spam tool caused.<br>
<br>
TB 60 saw lots of incompatible add-ons left working because they
were already installed and working, even though it would not
reinstall them. And while a policy might be relevant, it does not
fix the issue of anti virus products just force loading their
choices on startup. Compatible or not.
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1314555">https://bugzilla.mozilla.org/show_bug.cgi?id=1314555</a><br>
<br>
I think really that a compatibility reporter type link should exist
so that we can mark add-ons that are know to cause issues with
particular versions. But whilst ever it is a common practice to
modify the maxversions of files to get them to install, I do not
think we need a policy. We need a better ecosystem.<br>
<br>
You have a few bugs. Multiply that by a large number and you will
see the number of disgruntled folk in support forums. But their
complaint is we broke their favourite add-on. Just as failure to
get mail after update is our problem, not that if their rubbish
firewall. They will try anything to "just make it work". It is the
"feature" that makes Thunderbird usable for them.<br>
<br>
I think a more satisfactory model may be to simply remove from
public listing in web browser all add-ons that are not compatible
with the current version and only show relevant versions in the
add-on manager.<br>
<br>
Matt<br>
</body>
</html>