<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 05/10/2018 09:51, Óvári wrote:<br>
</p>
<blockquote type="cite"
cite="mid:90c083da-b295-e977-ba7e-3cdc4c1df0a0@zoho.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>When is it planned that Thunderbird will support "*" for the
maxVersion tag?<br>
<span class="blob-code-inner blob-code-marker-deletion"> <font
face="Courier New, Courier, monospace"><<span
class="pl-ent">em</span><span class="pl-ent">:</span><span
class="pl-ent">maxVersion</span>><span class="x
x-first
 x-last">*</span></<span class="pl-ent">em</span><span
class="pl-ent">:</span><span class="pl-ent">maxVersion</span>></font></span><br>
</p>
</blockquote>
<p>Personally, the only way I can see this ever happening is for
WebExtensions only - which would be ones that use just the
Thunderbird provided WebExtension APIs. Once WebExtension APIs are
confirmed/shipped they shouldn't be changing ever (in theory).</p>
<p>For other types of add-ons, I think this shouldn't happen -
anything can be changed in the core, and so a change could break
an add-on at any time, and an add-on author in that case should be
prepared to check for new versions & adverse effects.<br>
</p>
Mark<br>
</body>
</html>