PSA: Legacy extensions disabled by default on Nightly

[Kevin Jones]

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.

Like Mathieu replied on this thread (In order to get the install button
active):

"One workaround for this is to set "extensions.checkCompatibility.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."

On Mon, Aug 14, 2017 at 5:52 PM, Kev Needham <kneedham at mozilla.com> wrote:

> 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.
>
> Thanks.
>
> kev
>
>
>
> On 2017-08-14 4:20 PM, Kevin Jones wrote:
>
>> Hello Kev,
>>
>> The bugzilla site specifically requests any non-security issues related
>> to AMO be filed here:
>>
>> https://github.com/mozilla/addons
>>
>> and not on BMO.
>>
>> I'm not up to speed on github at the moment (don't recall my
>> credentials), but the STR should be pretty simple, just use latest
>> Nightly to go to any legacy addon page and you'll see the install button
>> is greyed out.
>>
>> On Mon, Aug 14, 2017 at 4:55 PM, Kev Needham <kneedham at mozilla.com
>> <mailto:kneedham at mozilla.com>> wrote:
>>
>>     Hi Kevin,
>>
>>     I was wondering if you had filed a bug for this and, if so, what the
>>     bug number is.
>>
>>     I'm particularly interested in the steps to repro the update problem
>>     you mention around updates, because the expectation is they should
>> work.
>>
>>     Could you let me know if you filed and, if not, a little more info
>>     on where updates don't work and I will try to repro and file?
>>
>>     Thanks much,
>>
>>     kev
>>
>>
>>     On 2017-08-13 5:20 AM, Kevin Jones wrote:
>>
>>         Thanks Andrew :-)
>>
>>         I want to mention that on the AMO site, legacy addons now appear
>>         with a
>>         greyed-out "install" button.  This happens when even in Nightly
>> with
>>         `extensions.legacy.enabled=true`.  The pref works and I can run
>>         legacy
>>         extensions, but the AMO site does not allow the user to install
>>         updates,
>>         including fixes for addons broken by removal of deprecated code.
>>
>>         "there is a preference that Nightly users can flip to re-enable
>>         loading
>>         of legacy extensions in the addons manager"
>>
>>         I don't seem to find anything in the addon manager to accomplish
>>         this, I
>>         had to take a guess at the name of the pref and flip it manually.
>>
>>         Kudos for another major step in the advancement into the next era!
>>
>>         Kevin
>>
>>         On Thu, Aug 10, 2017 at 10:00 AM, Andrew Swan <aswan at mozilla.com
>>         <mailto:aswan at mozilla.com>
>>         <mailto:aswan at mozilla.com <mailto:aswan at mozilla.com>>> wrote:
>>
>>
>>             After lots of recent discussion, it is finally happening.
>>         The patch
>>             to flip the default setting to disallow legacy extensions is
>> in
>>             autoland at the moment and, barring some snafu, should be in
>>             tomorrow's Nightly builds.  This is a bit anti-climactic
>>         since a few
>>             other changes that have already landed that broke a bunch of
>>             existing extensions.
>>
>>             Also this has been discussed in a few other threads but
>>         repeating
>>             here for folks that may have missed it: there is a
>>         preference that
>>             Nightly users can flip to re-enable loading of legacy
>>         extensions in
>>             the addons manager (of course this setting won't magically
>> make
>>             extensions that rely on the sdk or any changed internal
>>         interfaces
>>             work).  We will continue to honor this preference in Nightly
>>         builds
>>             and in unbranded builds, but when 57 (and later versions) go
>>         to beta
>>             and eventually to release, that preference will be ignored.
>> If
>>             you're familiar with addon signing and the circumstances in
>>         which we
>>             allow it to be disabled, legacy extensions are handled in
>>         the same way.
>>
>>             If you notice any problems or have questions, you can contact
>> me
>>             directly, use the dev-addons mailing list, or drop into
>>             #webextensions on IRC.
>>
>>             :highfive:s all around!
>>
>>             -Andrew
>>
>>
>>             _______________________________________________
>>             Dev-addons mailing list
>>             Dev-addons at mozilla.org <mailto:Dev-addons at mozilla.org>
>>         <mailto:Dev-addons at mozilla.org <mailto:Dev-addons at mozilla.org>>
>>             https://mail.mozilla.org/listinfo/dev-addons
>>         <https://mail.mozilla.org/listinfo/dev-addons>
>>             <https://mail.mozilla.org/listinfo/dev-addons
>>         <https://mail.mozilla.org/listinfo/dev-addons>>
>>
>>
>>
>>
>>         _______________________________________________
>>         Dev-addons mailing list
>>         Dev-addons at mozilla.org <mailto:Dev-addons at mozilla.org>
>>         https://mail.mozilla.org/listinfo/dev-addons
>>         <https://mail.mozilla.org/listinfo/dev-addons>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/dev-addons/attachments/20170814/c3a36d1d/attachment-0001.html>