Mozilla Firefox/Thunderbird “legacy” addons (#E6F3)

News from the friendly crackpots over at Mozilla:

Hello,

 

You are receiving this email because you are listed as a developer of a legacy add-on on addons.mozilla.org (AMO). Mozilla will stop supporting Firefox Extended Support Release (ESR) 52, the final release that is compatible with legacy add-ons, on September 5, 2018.
 
As no supported versions of Firefox will be compatible with legacy add-ons after this date, we will start the process of disabling legacy add-on versions on AMO. On September 6, 2018, submissions for new legacy add-on versions will be disabled. All legacy add-on versions will be disabled by early October 2018. Once this happens, users will no longer be able to find your legacy versions on AMO.
 
After legacy add-ons are disabled, you will still be able to port your extension to the WebExtensions APIs. Once your new version is submitted to AMO, users who have previously installed your extension will automatically receive the update and your listing will appear in the gallery.
 
You can find more information about porting legacy extensions to the WebExtensions API on MDN, and we encourage you to visit our wiki for more information about upcoming development work and how to get in touch with our team if you need any help.
 
Regards,
 
The Add-ons Team
 
You have received this email because you are a registered add-on developer on addons.mozilla.org and you have at least one legacy extension associated with your account. If you do not want to receive these updates about your AMO account and legacy extensions, please sign in to addons.mozilla.org and remove your legacy extensions.
 
Mozilla
331 E. Evelyn Avenue
Mountain View, CA 94041
Mozilla Privacy Notice
addons@e.mozilla.org

Well, thank you very much. Firefox is down to 10% global market share (from…40?) because of massive design fails, and now you idiots will halve that again with the stupid forced Webex addon thing and kicking out all “legacy” XUL addons. Good luck, I can stay basically forever on FF 52.9 and TB60. Or I can change to Chrome, like half of the world has already done. Great idea to prefer hated UI redesign over speed improvements, fixes of memory holes or just plain integration of must-have features that had to be delivered for ages by popular addons.

Here’s the summary for Thunderbird:
* If you’re using up to TB57 (most people should be at TB52 ESR), use version 64.3 from the archive. Even though Mozilla may state that there are no compatible versions: There ARE. 64.4+ will NOT work.

* If you’re using TB58+ (TB60 is current as of now, which was released on August 6th), use version 64.4 or newer, basically whatever your TB will offer you for installation. 64.3- will NOT work.

How did I know there’s a new Thunderbird release? Easy! Just watch the blog access numbers go through the roof:

(This post wraps up the former #E6/#E6F1 and #E6F2 posts that still contain the files for manual downloading…let’s say for the unlikely event that Mozilla will take them down as well.)


6 Responses to Mozilla Firefox/Thunderbird “legacy” addons (#E6F3)

  1. Dan C. says:

    Thank you for clearing this up in Plain English! I’m currently running TB 52.9.1 (32-bit). So when I get to TB58+ that’s when I have to start to use your version 64.4+ TFSC. :good:

    Thanks!

    Dan C.
    Staten Island, NY

  2. DavidBE says:

    Hi. I’m on the Thunderbird Beta, and was updated last night to 63.0b1. Most of my add-ons were automatically disabled and marked as incompatible. TFSC – I was running 64.4 – wasn’t, but there’s a problem. All the text in TB shrunk, as if TFSC wasn’t working or had all been set back to default values, and the toolbar button has disappeared, as has the entry in the tools menu, leaving no way to call it up and view/change any settings in it. The add-on options are still accessible, but that just gives the options to hide the tools and app menus and abbreviate the toolbar button text. I discovered that there was a TFSC version 64.5 and installed that, but it has made no difference – I still have no toolbar button or entry in the tools menu. Is there a TB config file setting I can check and/or a TFSC config file I can maybe load and edit in a text editor? At the moment I’m trying to figure out what settings to put in a userChrome.css file to get back to the display i want, but I’d much rather have a working TFSC if possible – for which, much thanks.

    • Bzzz says:

      I’ll have a look into the beta version later today. There’s not much in the changelogs…

      ADD-ON SUPPORT: Restartless add-ons continue to work if their authors have made the necessary minor adjustments. Non-restartless legacy add-ons using XUL overlays are only supported if add-on authors have adapted them, and Lightning/Calendar is the only one we know that has been adapted.

      but maybe there will be an useful error message in the logs. We’ll see.
      Version 64.5 is just a minor tweak, mostly with removed legacy code. Both 64.4 and 64.5 work fine for me with TB60.2.1, which reportedly does cause trouble, probably only under Windows 10. I’m using Win7 for troubleshooting, if that matters.

      • DavidBE says:

        I went from TB 60 beta 11 (which should have been very nearly the same if not actually the same as 60.2.1 as it was the last beta before the 60.2.1 general release) to 63.0 beta1. TFSC 64.4 did work fine with TB 60b11 for me, and that’s on a Windows 10 machine. I did see what you quoted above in the changelogs, so was a bit surprised that TFSC plus one other add-on weren’t disabled after the update to 63b1, when 6 other add-ons were. But then found it wasn’t working as I described above. If there’s any trouble shooting I can do, finding and reading of logs or whatever, please let me know.

      • Bzzz says:

        Okay, so here’s the deal: XPCOMUtils.generateQI seems broken in both Firefox and Thunderbird nightlies, probably even in the beta versions. See for example https://github.com/mozilla/tls-canary/issues/171
        As the addon crashes on startup with exception “TypeError: XPCOMUtils.generateQI is not a function”, I’d say that’s true for 63b1, and therefore it won’t work.

        If you’re not a developer, go back to a stable version, if you’re a dev – well, deal with it ;) Not trying any bugfixing around a fuckup in beta TB versions, sorry.

        • DavidBE says:

          OK, thanks for looking and explaining. I switched to the beta tracks a few months ago because it contained a fix for something that had been annoying me, and some other features that were nice. All of that is now in the new stable version, and I can’t see anything else in the new beta I’m bothered about, so I will go back to the stable track for now. Thanks again for creating this add-on.

Leave a Reply

Your email address will not be published. Required fields are marked *

:mrgreen: 
:neutral: 
:twisted: 
:arrow: 
:shock: 
:smile: 
:???: 
:cool: 
:evil: 
:grin: 
:idea: 
:oops: 
:razz: 
:roll: 
;-) 
:cry: 
:eek: 
:lol: 
:mad: 
:sad: 
:suspect: 
:!: 
:?: 
:bye: 
:good: 
:negative: 
:scratch: 
:wacko: 
:yahoo: 
:heart: 
B-) 
:rose: 
:whistle: 
:yes: 
:cry2: 
:mail: 
:-(( 
:unsure: 
:wink: