Addon Compat. Reporter Messy Addons labels ("LEGACY"...)

[DN123ABC]

Does anyone else think it would be helpful to do the Addons Manager in a matrix layout?

I'd like to see a column including version number, "LEGACY" (or not), and also "WEBEXT" (or not).

Using version 56 right now, and I think that does both "LEGACY" as well as "WEBEXT" addons.

There is also a setting/field called "Compatible with multiprocess" ("Not compatible with multiprocess").

These are all in helter-skelter order around the screen, and it would be nice to see them laid out in a more orderly fashion. I imagine the data is all there, since it is now displayed, but it is not easy to see, since it depends on how long the extension name is, among other things.

Anyone?

[the-edmeister]

We're going thru a transition stage with Firefox 55 and 56. No point in thinking about for too long, come Firefox 57 the Legacy extensions will be disabled and WE will all that is allowed, unless you use with the Nightly build.


.

[DN123ABC]

We're going thru a transition stage with Firefox 55 and 56. No point in thinking about for too long, come Firefox 57 the Legacy extensions will be disabled and WE will all that is allowed, unless you use with the Nightly build.

This is what I am talking about. It would make it easier to keep track of what is fixed or working, and what is not. Either way, it would help to show the versions and any/all information in a more organized fashion, either before or after version 56 and 57.

Thanks for letting me clear this up.

[Grumpus]

There is this link with current working /non-working/being fixed information.
are we web extensions yet

[lovemyfoxy]

What's Mz's purported reason for making the changes? What's the Nightly Build (briefly,) and how does it compare to ESR?

[smsmith]

What's Mz's purported reason for making the changes?

https://support.mozilla.org/en-US/kb/fi ... =inproduct

What's the Nightly Build (briefly,) and how does it compare to ESR?

Nightly builds are alpha software, with a new "build" or "daily snapshot" created everyday. It can be unstable and is not recommended for everyday use unless you like to live on the edge. Firefox release is v55. Nightly is v57. Before features and fixes make it into release, they filter down from Nightly and are improved or removed before being released. It does not compare to ESR in any way. ESR is the exact opposite of the Firefox spectrum.

[DN123ABC]

I just realized one of these labels comes from a separate extension: Addon Compatibility Reporter 2.2.4, which is ITSELF INCOMPATIBLE! ("LEGACY")

You'd think someone touting a COMPATIBILITY REPORTER would try to stay more current!

[lovemyfoxy]

What's Mz's purported reason for making the changes?

https://support.mozilla.org/en-US/kb/fi ... =inproduct

Thanks for clarifying that.. Mz's destroying many add-ons to make others compatible. And I suppose they don't approve of all the chrome tweaks we've done either. Meaning they're no longer happy that we're open-source.

Can this be removed from our mission statement: "...but we love them just the same."

[James]

What's Mz's purported reason for making the changes?

https://support.mozilla.org/en-US/kb/fi ... =inproduct

What's the Nightly Build (briefly,) and how does it compare to ESR?

Nightly builds are alpha software, with a new "build" or "daily snapshot" created everyday. It can be unstable and is not recommended for everyday use unless you like to live on the edge. Firefox release is v55. Nightly is v57. Before features and fixes make it into release, they filter down from Nightly and are improved or removed before being released. It does not compare to ESR in any way. ESR is the exact opposite of the Firefox spectrum.

To add Nightly is not tied to any one version as it is one of the development channels as it used to be Release < Beta < Aurora(developers edition) < Nightly and now it is Firefox < Beta < Nightly. Before this Mozilla used to use codenames for versions being developed but stopped from Fx 4.0 and on. A ESR version has its own channel for updates.

[WaltS48]

What's Mz's purported reason for making the changes?

Here are three.

• Taking advantage of new technologies like Electrolysis and Servo
  Protecting users from spyware and adware
  Shortening the time it takes to review add-ons

REF: The Future of Developing Add-ons

[DN123ABC]

Is there a similar extension for Addon Compatibility Reporter, which helps people migrate to version 57?

[Brummelchen]

there is no migration possible - written so many times - legacy is a complete other modell. you have to search on your own if there is a replacement. ACR dont know about webextensions.

but if you have a closer look - firefox is offering a link to find a replacement as webextension - you should click it.