<div dir="ltr">No. If you can get a link to the addon, it will install it. And it will run as long as `extensions.legacy.enabled` is true.<br><br>Like Mathieu replied on this thread (In order to get the install button active):<br><br>"One workaround for this is to set "extensions.checkCompatibility<wbr>.nightly"
to false in about:config. This will force nightly to ask AMO to ignore
compatibility information when updating extensions. Do this at your own
risk though, ignoring compatibility usually leads to broken add-ons."</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 14, 2017 at 5:52 PM, Kev Needham <span dir="ltr"><<a href="mailto:kneedham@mozilla.com" target="_blank">kneedham@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ah, I thought you were saying updates to installed add-ons don't work. That'd be a bugzilla request, because it'd be a firefox issue. I misunderstood.<br>
<br>
Thanks.<br>
<br>
kev<br>
<br>
<br>
<br>
On 2017-08-14 4:20 PM, Kevin Jones wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello Kev,<br>
<br>
The bugzilla site specifically requests any non-security issues related<br>
to AMO be filed here:<br>
<br>
<a href="https://github.com/mozilla/addons" rel="noreferrer" target="_blank">https://github.com/mozilla/add<wbr>ons</a><br>
<br>
and not on BMO.<br>
<br>
I'm not up to speed on github at the moment (don't recall my<br>
credentials), but the STR should be pretty simple, just use latest<br>
Nightly to go to any legacy addon page and you'll see the install button<br>
is greyed out.<br>
<br>
On Mon, Aug 14, 2017 at 4:55 PM, Kev Needham <<a href="mailto:kneedham@mozilla.com" target="_blank">kneedham@mozilla.com</a><br>
<mailto:<a href="mailto:kneedham@mozilla.com" target="_blank">kneedham@mozilla.com</a>>> wrote:<br>
<br>
Hi Kevin,<br>
<br>
I was wondering if you had filed a bug for this and, if so, what the<br>
bug number is.<br>
<br>
I'm particularly interested in the steps to repro the update problem<br>
you mention around updates, because the expectation is they should work.<br>
<br>
Could you let me know if you filed and, if not, a little more info<br>
on where updates don't work and I will try to repro and file?<br>
<br>
Thanks much,<br>
<br>
kev<br>
<br>
<br>
On 2017-08-13 5:20 AM, Kevin Jones wrote:<br>
<br>
Thanks Andrew :-)<br>
<br>
I want to mention that on the AMO site, legacy addons now appear<br>
with a<br>
greyed-out "install" button. This happens when even in Nightly with<br>
`extensions.legacy.enabled=tru<wbr>e`. The pref works and I can run<br>
legacy<br>
extensions, but the AMO site does not allow the user to install<br>
updates,<br>
including fixes for addons broken by removal of deprecated code.<br>
<br>
"there is a preference that Nightly users can flip to re-enable<br>
loading<br>
of legacy extensions in the addons manager"<br>
<br>
I don't seem to find anything in the addon manager to accomplish<br>
this, I<br>
had to take a guess at the name of the pref and flip it manually.<br>
<br>
Kudos for another major step in the advancement into the next era!<br>
<br>
Kevin<br>
<br>
On Thu, Aug 10, 2017 at 10:00 AM, Andrew Swan <<a href="mailto:aswan@mozilla.com" target="_blank">aswan@mozilla.com</a><br>
<mailto:<a href="mailto:aswan@mozilla.com" target="_blank">aswan@mozilla.com</a>><br>
<mailto:<a href="mailto:aswan@mozilla.com" target="_blank">aswan@mozilla.com</a> <mailto:<a href="mailto:aswan@mozilla.com" target="_blank">aswan@mozilla.com</a>>>> wrote:<br>
<br>
<br>
After lots of recent discussion, it is finally happening.<br>
The patch<br>
to flip the default setting to disallow legacy extensions is in<br>
autoland at the moment and, barring some snafu, should be in<br>
tomorrow's Nightly builds. This is a bit anti-climactic<br>
since a few<br>
other changes that have already landed that broke a bunch of<br>
existing extensions.<br>
<br>
Also this has been discussed in a few other threads but<br>
repeating<br>
here for folks that may have missed it: there is a<br>
preference that<br>
Nightly users can flip to re-enable loading of legacy<br>
extensions in<br>
the addons manager (of course this setting won't magically make<br>
extensions that rely on the sdk or any changed internal<br>
interfaces<br>
work). We will continue to honor this preference in Nightly<br>
builds<br>
and in unbranded builds, but when 57 (and later versions) go<br>
to beta<br>
and eventually to release, that preference will be ignored. If<br>
you're familiar with addon signing and the circumstances in<br>
which we<br>
allow it to be disabled, legacy extensions are handled in<br>
the same way.<br>
<br>
If you notice any problems or have questions, you can contact me<br>
directly, use the dev-addons mailing list, or drop into<br>
#webextensions on IRC.<br>
<br>
:highfive:s all around!<br>
<br>
-Andrew<br>
<br>
<br>
______________________________<wbr>_________________<br>
Dev-addons mailing list<br>
<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a> <mailto:<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a><wbr>><br>
<mailto:<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a> <mailto:<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a><wbr>>><br>
<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/dev-addons</a><br>
<<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/list<wbr>info/dev-addons</a>><br>
<<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/list<wbr>info/dev-addons</a><br>
<<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/list<wbr>info/dev-addons</a>>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Dev-addons mailing list<br>
<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a> <mailto:<a href="mailto:Dev-addons@mozilla.org" target="_blank">Dev-addons@mozilla.org</a><wbr>><br>
<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/dev-addons</a><br>
<<a href="https://mail.mozilla.org/listinfo/dev-addons" rel="noreferrer" target="_blank">https://mail.mozilla.org/list<wbr>info/dev-addons</a>><br>
<br>
<br>
</blockquote>
</blockquote></div><br></div>