Skip to content
This repository has been archived by the owner. It is now read-only.

[Legacy add-ons] - XUL/XPCOM support ends with Firefox 57 - add-ons like CTR will stop working - add-ons will be 'disabled' in October 2018 and won't be publically available anymore on AMO #299

Aris-t2 opened this issue Dec 16, 2016 · 273 comments


Copy link

@Aris-t2 Aris-t2 commented Dec 16, 2016

If you want to use Classic Theme Restorer (and other legacy add-ons) up to summer 2018, I suggest to switch to Firefox ESR channel. Firefox 52 ESR gets all security updates default Firefox gets without changing base code and without new add-on breaking changes. From 2018-06-26 on there won't be any official up-to-date Firefox, that runs legacy add-ons anymore.

Moving to Firefox 52 ESR after installing Firefox 55/56 might break your browser profile. It is recommended to move to Firefox 52 ESR before Firefox 55 release (2017-08-08).

Waterfox and Basilisk browsers (based on Firefox code) will keep legacy add-on support.

Release schedule update: Fx 60 will become ESR instead of 59.

Difference between Extended Support Release channel and default channel:
Fx 52.0 ESR = Firefox 52 (first major code changes since Firefox 45.0 ESR)
Fx 52.1 ESR = Firefox 53 (without major code changes since Fx 52, but with security updates from Fx 53)
Fx 52.2 ESR = Firefox 54 (without major code changes since Fx 52, but with security updates from Fx 54)
Fx 52.7 ESR = Firefox 59 (without major code changes since Fx 52, but with security updates from Fx 59)
Fx 52.8 ESR = Firefox 60 (without major code changes since Fx 52, but with security updates from Fx 60)
Fx 52.9 ESR = Firefox 61 (without major code changes since Fx 52, but with security updates from Fx 61)
Fx 60.0 ESR = Firefox 60 (first major code changes since Firefox 52.0 ESR)
Fx 60.1 ESR = Firefox 61 (without major code changes since Fx 60, but with security updates from Fx 61)

Release dates:
[2018-01-23] Firefox 58 / ESR 52.6
[2018-03-13] Firefox 59 / ESR 52.7
[2018-05-08] Firefox 60 / ESR 52.8 / ESR 60
[2018-07-03] Firefox 61 / ESR 52.9 / ESR 60.1
[2018-08-28] Firefox 62 / ESR 60.2 -> end of life for legacy add-ons

If you are on Firefox ESR 52.7, you should get an offer to upgrade to Firefox ESR 60.0 on 2018-05-08. If you decline that offer, Firefox will just update to Firefox ESR 52.8.
This will be repeated for one more cycle (Firefox ESR 52.9). From 2018-08-28 Firefox ESR 60.2 will be the only up-to-date and "secure" ESR version of Firefox and ESR 52.x will be deprecated.



You are receiving this email because you are listed as a developer of a legacy add-on on (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 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[3], and we encourage you to visit our wiki[4] for more information about upcoming development work and how to get in touch with our team if you need any help.


The Add-ons Team

CTR and other legacy add-ons will stop working on Firefox 57 when WebExtension will replace legacy add-ons and XUL/XPCOM support will be removed for add-ons completely. CTR (and all of my other Firefox add-ons on AMO) can not survive this change.

Even if it will be possible to port some of CTRs currently over 400 tweaks/options/features to WebExtensions one day (currently none of them would work in a XUL free environment), I have no plans to do that. The outcome would not be CTR anymore.

At the moment more and more Firefox 57 features land on Firefox Nightly. As a result some CTR features stopped working on Firefox 55/56 Nightly. They work on Firefox 55 beta and also might work on Firefox 56 beta and on Firefox 55/56 release builds.

CTR had to drop support so far for:

  • custom general bookmark icons in Firefox 55
  • old search in Firefox 56 Nightly (it might return for Firefox 56 beta and release)

WebExtensions may be the future for web content add-ons (according to Mozilla), but losing powerful ui customization ability on user level is definitively the biggest step back Firefox ever made. It loses the only advantage it has over ALL other browsers.

Additional explanation to this statement: On some comments areas on various websites protectionists of WebExtensions claim by quoting the previous sentences I have not understood how future development of applications works, blabbing applications have to drop "old ballast" in order to reinvent themselves and offer new technologies and other nonsense. Those ignorant protectionists (like Hauro) fail to understand, that CTR was and still is fully compatible to all so-called modern technologies added through time to Firefox like multi-process architecture, 64Bit architecture etc...
The only reason why CTR does not work in Firefox 57+ is Mozillas decision to take away add-ons almighty power over the browser, not because add-on features are incompatible to modern techniques or Firefox 57+ in general. A simple CSS loader would allow over 80% of CTRs features to be available for Firefox 57+. This is proven by all userChrome.css/userContent.css tweaks available here.

This also applies to my other add-ons like Classic Toolbar Buttons, NoiaButtons and GlassMyFox. NoiaButtons for example could be fully ported to userChrome.css and is working in Firefox 57+ just fine.

For now I will only try to keep my add-ons "alive" till the end of Fx 52 ESR, if I'm still allowed to upload updated legacy add-ons to AMO.

CTR and other add-ons should still work on Firefox 52 ESR until Firefox 59 ESR replaces it in 2018 (~Q2). Waterfox should also support legacy add-ons indefinitely.

Are we WebExtensions yet?
APIs > Legend > complete

pretty much all the APIs that it makes sense to implement have been done. What remains is undocumented, deprecated or we've thought not worth bothering with (we could be wrong).

In case you are wondering why some add-ons have to go: according to Mozilla and Firefox devs they [add-ons, APIs] are not worth bothering with.

Add-ons in 2017

Classic Theme Restorer may be dead by the end of 2017

Old Firefox Extensions Will Stop Working in Firefox 57

The Dev-addons Archives

Bug 1328244 - [WebExtensions] Firefox customization API request - WONTFIXed by Mozilla

The Road to Firefox 57 – Compatibility Milestones

Quick summary of what’s already been discussed on that post and the comments:

  1. Starting with 57, many things will break that will also break add-ons. Most add-ons that aren’t WebExtensions will be broken regardless. Aligning with ESR is not a goal.
  2. WebExtensions will never do everything XPCOM does, so feature parity is not a goal. Some top add-ons can’t be completely ported (DownThemAll and Firebug come to mind) and we’re accepting that risk.

Keep in mind: Mozilla decided to end current powerful browser customization not the add-on developers! It is still unknown what will be possible with upcoming APIs in the future.

Firefox 57+ tweaks

As long as userChrome.css is supported, we can get rid of Photon UI by modifying existing stuff. We can not add anything new to the UI though.

Promo of what I have tested so far (on Win7 with AeroBlue colors, possible on other OSs too)

More here: #365

@Aris-t2 Aris-t2 added the wontfix label Jan 16, 2017
Copy link

@orbea orbea commented Jan 29, 2017

So...firefox is dead? How about porting it to palemoon? There is a lot of theme stuff that needs to be fixed there even if they dont have australized...

Copy link
Owner Author

@Aris-t2 Aris-t2 commented Jan 29, 2017

Palemoon does not need CTR. All important CTR features are part of Palemoon by default, because Palemoon never switched to Fx29+ UI.

Copy link

@orbea orbea commented Jan 29, 2017

Well, I kind of disagree. There is a lot wrong with palemoon that CTR has fixed in firefox. Sure there are some stand alone addons that may work, but they don't come close to covering all the bases. For example everything from tab width to how the palemoon button doesn't move nor it is possible to change it to an icon as far as I can see.

To help explain, here is a semi-recent scrot of my firefox.

Your position is fully understandable, but bluntly I feel like I been given the short end of the stick and then mozilla snatched it back just to break it in half...

@Aris-t2 Aris-t2 changed the title CTR will stop working when Mozilla drops XUL/XPCOM support with the release of Firefox 57 CTR and other add-ons will stop working when Mozilla drops XUL/XPCOM support with the release of Firefox 57 Jan 31, 2017
Copy link

@kyodev kyodev commented Feb 20, 2017

Thank you for your work @Aris-t2, mozilla has wasted your time and will annoy many users.
Not serious according to a mozilla master, only 40% of people use addons ... :( 👎

Copy link

@vasa1 vasa1 commented Feb 25, 2017

CTR made Firefox usable for me despite Australis.

My sincere thanks to you for having created and maintained it so diligently.

Copy link

@RobertZenz RobertZenz commented Feb 25, 2017

@kyodev To be blunt, online petitions are bullshit. I do not recall a single instance where an online petition did achieve something. Also, developers of very popular addons (DownThemAll, CTR, QuickSaver and a few others) have been throwing their weight at that decision, and have been either ignored or told that the plan will be executed as planned. Combined these addons have millions of users (maybe even tens of millions), and now Mozilla should care about an online petition with 100 signatures?

Copy link

@kyodev kyodev commented Feb 25, 2017

you know what? I think you're right ... :(
Is it always better than to grumble without doing anything? no? Never mind.
Hope makes it live? a little

Copy link

@msamez msamez commented Feb 27, 2017

Well, fuck. I was just customizing a new Firefox installation when I noticed this message. Finding the out add-on will go away because of yet another terrible decision by Mozilla is baffling and disappointing. And concerning too, because I've become super comfortable with how I can get Firefox to look and behave and now I have no idea what browser I'm going to have to switch to in the future. It's just completely unusable for me without the add ons.

Copy link

@RobertZenz RobertZenz commented Feb 27, 2017

@kyodev To clarify. I do believe that people can make change happen if they want to, however, I do not believe that slapping your name on an online list and being done with it will do anything, anywhere, anytime. If you want a change, look up if somebody else requested it already and what the state is, if not, state your case to the right people (firefox-dev and dev-addons mailing list, in this case). But don't believe that slapping your name on an online petition will achieve anything (just like slapping "+1" on a feature request will not make the coder go faster, or saying "this software is terrible" will magically make the software better with the next version).

For everyone else, Mozilla seems to beg down a little in this regard, as they are hinting that there will be APIs in the future to change the appearance of Firefox from addons, I wouldn't hold my breath, though. My question on the dev-addons list can be found here.

Copy link
Owner Author

@Aris-t2 Aris-t2 commented Feb 27, 2017

"Some kind of theming" will be possible even after Firefox 57 arrives, but it will be highly restricted. No "I can do what I want" anymore with CSS, JavaScript or XML/XUL-similar stuff. No more moving around stuff Mozilla does not want you to move around (buttons in titlebar, location bar, status area etc.).

Changing toolbar, tab and icon colors (maybe even icons later -> unknown) and using squared tabs will be possible. Look at current Nightly builds and the available "Compact" themes for example.


This however still means add-ons like CTR won't survive and rebuilding something that has two or three of over 400 features just seems wrong and not worthy of being called CTR.

Copy link

@Mincegamer Mincegamer commented Mar 5, 2017

I've used CTR since Mozilla introduced Australis and took away a lot of the old features I liked. I install it on every computer I use Firefox on. This may be a dumb question, but I am sure it will be possible to stay on Firefox 56 for as long as I want, just like many Opera users did when they killed that browser too. Therefore, it will still be possible to use the final released version of this addon, correct? I know the browser will grow more out of date every day, but I imagine I will cross that bridge when it arrives, like many people.

I'm sure the people here already agree completely, but I don't think I can ever use Firefox once they kill off these old addons. I absolutely HATE the new search in particular, and without CTR to change back to the dropdown search, I would be better off just using Chrome at that point. That is Mozilla's goal I guess =].

Copy link

@kyodev kyodev commented Mar 5, 2017

perhaps, it would be better to swith to firefox 52esr (issue in avril 2017)
support and security fix fo approximately one year, after ...

Copy link

@ghost ghost commented Mar 14, 2017

Another nail in the FF coffin. Mozilla seem determined to continue to ruin Firefox till no one uses it - apart from fanboys.
RIP FF - you were great once.

Copy link

@allo- allo- commented Mar 28, 2017

Wait some time, what happens after the release. I guess there will be many extension developers and their users, which try to revolt against the change, when their favourite extensions suddenly become useless. Something will happen.

I think there will be quite a few forks of firefox, but i see that it's too hard to maintain a firefox fork for most people. I see with palemoon, that they probably won't keep up, if they aren't already vulnerable to things fixed in recent firefox. But with such a breaking change, there is a chance, that quite a few volunteers from the mozilla community organize and make more possible than the people, which were just annoyed by a ugly default theme.

When the last ESR becomes unsupported we will see what has developed until then, which forks, patchsets, etc. are available as alternative. I still do not believe, that the many many extension developers and power users will silently accept the change.

Which doesn't mean, that WebExtensions are bad. E10S, Multiprocess and WebExtensions are great and XUL is probably not the best solution for making a gui extendable without breaking extensions on major changes in the gui. But the solution is to abandon it, after there are WebExtension APIs, which allow the same amount of customization. Which is quite possible, but seems unwanted at the moment.

Copy link

@karlo2105 karlo2105 commented Mar 30, 2017

When Firefox switched to Australis, I started to use your CTR addon and that was the only reason I kept on with Firefox. I can't stand Chrome look-alike interface.
For now, I am testing Seamonkey, it looks like Firefox at it used to be on its debut. I hope you will port your addons to Seamonkey and or Palemoon.
I stand with Firefox as long as your CTR works.

Firefox used to be synonym for freedom which is lesser and lesser case.
I encourage you to keep on with your addon maintenance. ;)

Copy link

@ArkadiuszMichalski ArkadiuszMichalski commented May 4, 2017

Per this doc ( old extensions will still work in Nightly (even not e10s compatibile), but how long I don't know. Maybe there will be some workaround turn them on also for beta / release (like we have for unsigned addon).

Copy link
Owner Author

@Aris-t2 Aris-t2 commented May 4, 2017

Only in theory. The massive changes will break them anyway.

@Aris-t2 Aris-t2 removed the wontfix label May 8, 2017
Copy link

@Keatah Keatah commented Jun 12, 2017

Once CTR and the ability to customize stop working I will stop using Firefox. Totally dislike Australis and anything flat or "Chromish". And CTR is the only reason I stuck with FF since it came out, essentially..

Too many changes made just to make them..

Copy link

@MelchiorGaspar MelchiorGaspar commented Jun 17, 2017

The scrapping of the BEST PART of Firefox the, "XUL/XPCOM " based extension system for SOMETHING TOTALLY INFERIOR TO IT...


I heard they even fired their original CEO...

My entire LIFE revolves around Firefox.. so I will NOT be able to upgrade beyond FF v56 probable for the rest of my natural life... MOZILLA!!!!!!!!!!!!!!!!!!!!!!!!! IDIOTS!!

end rant! loi ;p

Copy link

@evan-king evan-king commented Jun 23, 2017

Rapid release cycles were theoretically a good process improvement, but the turning point for Mozilla as a whole. Australis was the straw that broke my back. For anyone still on Firefox, I recommend you start now building up/getting comfortable with a profile in Pale Moon or some other suitable alternative. (By my estimation, Pale Moon is the closest approximation of Firefox when it was best at its core competencies, i.e. meaningful customization and catering to advanced users.)

However, do not rush to stop using Firefox before XUL/XPCOM support is removed. It's not likely to have an impact, but short-term usage metrics should clearly demonstrate the impact this has on their active user base. Words failed, so make Mozilla know they'll be the sole occupants of their brave new world by your actions.

Copy link

@allo- allo- commented Jun 23, 2017

@evan-king Something will happen. I think there will be a lot of forks, where most are dying pretty soon. Possibly some will survive.

The problem is, XUL may be hard to support without mozilla paying for a lot of manpower. And somebody will sooner or later need to exchange gecko for servo.
On the other hand, somebody has to support XUL to keep thunderbird alive, which depends on XUL and doesn't have any manpower left.
I heard they have some plans to migrate their interface to something based on HTML (not that soon, as far as i know) as well, but this will frustrate many users as well. So there are quite a lot people interested in XUL.

Copy link

@IMNdi IMNdi commented Jun 28, 2017

The petition is dead and will be dead. 240 sigs in 3 months. Nobody knows, nobody cares and will keep on not caring until everything breaks.

Browsers nowadays are treated like phone OSs. What you do matters not, what matters is "apps". What can you do, what can't you do, how buttery smooth you are.

Soon, all the "apps" are gonna break and when they do Firefox is going to be gone. Market share is declining because the addons keep dying, I think I lost all my favorites in the last couple years. When it finally kills them and it simplifies the look, it will finally be the poor man's Chrome they always wanted and finally be laid to rest because nobody wants a poor man's Chrome when Chrome is free.

IMO, Firefox started dying off when they opted to take away my manual history limit because people's histories made Firefox slow. The shift in mentality is what broke Firefox. You make history faster, you don't make my history "automatic". Videos auto-play? Get an addon or something. Crashes? Addon memory collection. Memory usage too large? 64 bit. To heck with fixing, we need VR support STAT!

Ah well. You know you're doing bad when Safari takes your market share.

Le roi est mort, vive le roi.

Copy link
Owner Author

@Aris-t2 Aris-t2 commented Feb 16, 2018

All Thunderbird add-ons will be moved to a different location in the near future. It was announced to add-on devs in an email in November 2017. A "" would be nice for Waterfox and Besilisk users, but who would host and maintain such a project?

Copy link

@grahamperrin grahamperrin commented Feb 16, 2018

… tried searching for it at the official places …

Reddit too often fails to find what's sought :-(

… (i.e. The Waterfox Blog), …

See What’s new in Waterfox 56.0? in Waterfox 56 Release (2017-11-30) but please note that corrections are in the pipeline.

… "" would be nice for Waterfox …

Legacy Extensions Database · Issue #303 · MrAlex94/Waterfox

Copy link

@hawkeye116477 hawkeye116477 commented Feb 16, 2018

Copy link

@Rafagd Rafagd commented Apr 12, 2018

I know this issue tracker is not supposed to be used for that, but I'd like to thank you for developing this extension and enabling me to keep my firefox looking like Firefox 2.0 for these short little years, before Mozilla ruined everything.

I made everything workout in the end with userChrome.css and one webextension, but I'm already seeing rumors that even userChrome.css is probably going to be removed at some point in the future too.

The fact that firefox is not the browser that has high customizability + the shady deals Mozilla has been making might finally force me to migrate to something else, but I'd like you to know that your extension kept me here a little longer. And kept my firefox looking like firefox instead of a poor man's version of chrome.

Copy link

@watchpocket watchpocket commented May 9, 2018

"If you are on Firefox ESR 52.7, you should get an offer to upgrade to Firefox ESR 60.0 on 2018-05-08. If you decline that offer, Firefox will just update to Firefox ESR 52.8."

In fact what happened with my upgrade today from Firefox ESR 52.7.3 is that I hit "Check for updates" in "Help" --> "About Firefox", and it just said "Update to ESR 52.8." I re-started and am now at ESR 52.8.0. There was no offer to upgrade to ESR 60.0, and that's fine with me. I'm mostly using Waterfox at this point anyway, though Waterfox has just a very few minor bugs still to work out. But for all intents & purposes I've reproduced my entire FF environment & all the extensions I use over to Waterfox. This is what I'll use going forward, but if I can keep FF ESR going until 2018-08-28, I will (since I still use FF 10-20% of the time). Oh, and thank you for CTR. It continues to be a life-saver on both FF and WF.

Copy link

@Rafagd Rafagd commented May 10, 2018

@watchpocket: I couldn't find a source for this, but I'm pretty sure Waterfox is going to update its codebase to Firefox 60, whenever that becomes the ESR version.

Edit: Just read some posts above mine, there are some links that discuss this.

Copy link

@watchpocket watchpocket commented May 10, 2018

So what are you saying are the consequences of that? Sure, Waterfox probably will update its codebase, but the important thing to me about Waterfox is that it will not abandon the XUL customizations that are so essential to all of us who for years have run very customized FF setups with lots of extensions -- the extensions that Firefox has now thrown to the trash heap, throwing a whole lot of sophisticated browser users away with them. Waterfox's creator is committed to keeping that.

Copy link
Owner Author

@Aris-t2 Aris-t2 commented May 10, 2018


The results of switching to Fx60 codebase while keeping xul compatibility might benefit everyone. I guess the idea behind this is having everything up to date feature wise from browser side and still being able to use legacy add-ons. We will see, if this requires rewriting add-ons or not once Waterfox 60 is out.

Copy link

@MelchiorGaspar MelchiorGaspar commented May 10, 2018

I like that idea... Waterfox could benefit from the faster quantum engine(s) in Firefox v57+
WHILE keeping the XUL extension system...

Copy link

@ExE-Boss ExE-Boss commented May 11, 2018

Also, Waterfox is also considering implementing my Gecko Elevated WebExtensions specification (ExE‑Boss/specifications#2)

Copy link

@NanhuGITHUB NanhuGITHUB commented Jul 19, 2018

CRITICAL NOTE: Firefox Is still Open Souce

Copy link

@NanhuGITHUB NanhuGITHUB commented Jul 25, 2018

@ExE-Boss Yay!

@Aris-t2 Aris-t2 changed the title Legacy add-ons like CTR will stop working when Mozillas XUL/XPCOM support ends with Firefox 57 release [Legacy add-ons] - XUL/XPCOM support ends with Firefox 57 - add-ons like CTR will stop working - add-ons will be 'removed' from AMO early October 2018 Aug 22, 2018
@Aris-t2 Aris-t2 changed the title [Legacy add-ons] - XUL/XPCOM support ends with Firefox 57 - add-ons like CTR will stop working - add-ons will be 'removed' from AMO early October 2018 [Legacy add-ons] - XUL/XPCOM support ends with Firefox 57 - add-ons like CTR will stop working - add-ons will be 'disabled' in October 2018 and won't be publically available anymore on AMO Aug 22, 2018
Copy link

@HarryhoInfo HarryhoInfo commented Sep 10, 2018

OK, ESR FF release is now version 60 and your great plugin dont work. What have we do?? Do you (or anybody) have some alternative?! Thanks.

Copy link

@MelchiorGaspar MelchiorGaspar commented Sep 10, 2018

@HarryhoInfo you could also change over to Waterfox which is holding on to XUL extension system..

Copy link

@HarryhoInfo HarryhoInfo commented Sep 14, 2018

@HarryhoInfo you could also change over to Waterfox which is holding on to XUL extension system..

Thank you very much, I am trying it!

Copy link

@mrnhmath mrnhmath commented Dec 1, 2018

Basilisk will have an add-ons site in the future, so it might be the new home for CTR. demo

Copy link
Owner Author

@Aris-t2 Aris-t2 commented Dec 1, 2018

Sure, once possible, I will submit latest CTR there too.

Copy link

@bawldiggle bawldiggle commented Jan 25, 2019

I am using Fox ESR 52.2.0 as secondary browser. In a moment of need I made it the primary browser.
Mozilla gremlins took over and auto updated v52.2.0 to ESR 60.4.0 DESPITE my settings to NEVER check for updates. All bookmarks, passwords and classic addons were obliterated.

If you want to use classic Fox never make it default browser, else Mozilla hijacks your PC and over rides any preferences to "never update". One workaround might be to block Fox phoning home ?
I used this technique to stop free WPS showing random ads when I least expected it.

PORTABLE VERSIONS SourceForge ( -- Windows only
32-bit only (because that is what PortableApps do)


Copy link

@MelchiorGaspar MelchiorGaspar commented Jan 25, 2019

@bawldiggle you could just switch over to use Waterfox

Copy link

@andrew-phi andrew-phi commented May 10, 2019

Thanks to everyone for lots of valuable information!
Other priceless addons like QuickJava and PoliceMan are too being destroyed by this API obsolence! Since Mozilla is governed by morons, and there seems to be no end to it, I'm looking towards PaleMoon now.

Copy link

@zahra21 zahra21 commented Jul 17, 2019

i have a question about xpcom and web extensions.
i wish to know, between classic versions of firefox, what is the first version that support web extensions?
i think its firefox 48. am i right?
how about firefox 50?

Copy link

@jabcreations jabcreations commented Jul 20, 2019

Aris, Alex was able to get some extensions working on Waterfox 68 Alpha. I'd have personally gone in and looked to see what code they changed though I don't have the time and the only responses I received were "Go figure it out yourself" however it seems possible. Once the pressure is off of me this is my absolute highest priority though it likely won't be for months at best. Any chance that you could please take a crack at it and see if even some of CTR will work with the alpha?

Copy link
Owner Author

@Aris-t2 Aris-t2 commented Jul 21, 2019

In theory CTR might work, if it gets rewritten to an restartless/bootstraped add-on like what "Classic Toolbar Buttons" add-on is/was or what "CustomizeMyBird" add-on currently is for Thunderbird 52.x-60.x.

However I spend hundreds of hours in creating CTR over time and I have no plans to recreate it again from the scratch. The scripts/styles for the Fx68 based browser version are present within my CustomCSSforFx and CustomJSforFx repositories here on Github and I do not have the time or the will to put them into an add-on again.

My time supporting Mozilla products through add-ons came to an end for Firefox with the release of Fx 57 and will end for Thunderbird with the release of Tb 68. Seamonkey seems to be dead for a while too.

Copy link

@smnthermes smnthermes commented Feb 23, 2020

SeaMonkey and Thunderbird just want to ride on Firefox release cycle.
Waterfox has been sold to System1, a U.S. pay-per-click ad company.
Pale Moon, Basilisk and Interlink Mail & News are well and alive.

I'd suggest @Aris-t2 to submit CTR and CMB to Pale Moon and Basilisk add-ons sites, and to Interlink Mail & News add-ons site, respectively. Don't believe in FUD being spread about these projects (debunked by 1, 2, 3, 4 and 5).

To quote Matt A. Tobin, developer of Unified XUL Platform:

We are the agents of our own salvation!

Copy link

@MelchiorGaspar MelchiorGaspar commented Feb 23, 2020

@smnthermes yeah I heard about Waterfox's sellout too on his blog... he makes it sound like its a good thing... idk...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet