<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 29/04/2016 8:37 AM, ISHIKAWA,chiaki
wrote:<br>
</div>
<blockquote class=" cite"
id="mid_bfbad23f_9555_6c67_ef07_f01127b9dea0_yk_rim_or_jp"
cite="mid:bfbad23f-9555-6c67-ef07-f01127b9dea0@yk.rim.or.jp"
type="cite">On 2016/04/29 4:52, R Kent James wrote:
<br>
<blockquote class=" cite" id="Cite_2079020" type="cite">Our
managing of addon updates is fairly problematic now in
Thunderbird,
<br>
as we rely on authors to test and update addons, but assume that
addons
<br>
are compatible by default. This results in a number of addons
that break
<br>
TB when installed on update.
<br>
<br>
Rather than just mark these as "not our problem" I suggest
instead that
<br>
we collect names and versions of addons that are known to break
core
<br>
Thunderbird functionality, and use a blocklist update to block
these. I
<br>
would not do that for addons whose functionality breaks, only
when the
<br>
addon breaks seemingly unrelated core functionality.
<br>
</blockquote>
<br>
So that means an addon called confirm-address that lets us
<br>
pause and take a look at addresses once again before a message
goes out
<br>
breaks in TB45 in that the check does happen, but in TB45 the mail
does not go out.
<br>
Since it does break core TB functionality (sending a message out)
<br>
but the functionality is very much related to the function of
addon,
<br>
this addon, confirm-address is not put into the blocklist?
<br>
<br>
I just need a clarification.
<br>
</blockquote>
<i>I would see that a a definite inclusion in the blocklist, mail
does not go out. <br>
If the check did not happen, and the goes out the core function
of sending mail is unaffected by the add-on failing to work as
advertised. So we do not block.</i><br>
</body>
</html>