<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 4/1/2019 12:43 PM, Andrei
Hajdukewycz wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3f91cbe2-b047-1fd9-b499-151a5174885e@thunderbird.net">On
2019-04-01 5:02 a.m., Jörg Knobloch wrote:
<br>
<blockquote type="cite">On 01 Apr 2019 13:34, Axel Grude wrote:
<br>
<blockquote type="cite">I wonder if there should be two download
buttons for extensions <=60 and >60 because it is
currently impossible to create an Add-on that satisfies both
requirements, and the majority of current Add-on users are on
Tb 60:
<br>
</blockquote>
<br>
Great mock-up. Yes, that would be ideal, but most likely not
easy to do. We should somehow revive the "beta capability", I
would feature the release version on the left and the beta
version on the right.
<br>
</blockquote>
Major modifications to the ATN UI are not going to happen any time
soon, especially not ones that involve strings, since we can't
localize those right now. I believe Geoff is working on a patch so
that the site will assume the browsing user is on the latest
release version of Thunderbird. That's about as good as it's going
to get.
<br>
<br>
In general the browser-based install workflow is so awkward and
underused that spending a lot of time on it makes no sense to me.
If it was simple to just disable it I think that would be even
better than trying to fix it. People should install add-ons via
Thunderbird. Either that or fix Thunderbird to register a custom
url protocol so that it could actually be linked directly to
install add-ons on click. But I assume there's some reason that
has never been done over the years. <br>
</blockquote>
Indeed, this takes us back to the year 2005
<a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=295462">https://bugzilla.mozilla.org/show_bug.cgi?id=295462</a><br>
</body>
</html>