Thanks LimboSlam. I just sent a PM to your add-ons guy Matt and I'll repeat part of it here.
There is one critical thing you have to understand about our IHG add-on. We have NO developers! Its original author tossed it in my lap about a year ago and said he wouldn't be back for 5-10 years. (Yes it is what it sounds like.) Another original developer has been gone for 2 years and recently returned, but is only interested in advising us and making comments. For several months we had what I amusingly call our "lead developer." He has been gone for more than a month and does not respond to emails nor has he even looked at our forum during that time. My only conclusion is that we have NO developers and NO capability of updating our code. We have no prospects for future developers. The version we have is very likely to be our final release.
If you change your browser in the future and IHG no longer works with it then there is no choice except to use an earlier version or quit using it, same as Firefox. Myself, I am a software developer and website designer, but my JavaScript skills are not up to understanding our code. Best I can do is modify our install.rdf and add a block for Pale Moon. Matt tells me Firefox add-ons are assumed to be equivalent to Pale Moon 24. I don't even understand why it work with 25.7.3.
I have been technical admin for our forum for about 2 years because I know our forum software SMF inside out. (I'm a mod package author for that software.) Early this year when our developer told me he would be leaving, he told me to keep it running if I want to. Unfortunately he did not leave me with the domain or Firefox add-ons website passwords. I moved it to my server and registered a new domain because I decided it would be unwise to just hope things would work out. I had intended to move back to our .COM domain when it expired but I found out it's on auto-renew.
So here I am. I'm in charge of an add-on project which I host on my own server and pay the domain registry fees myself, and refuse any donations, because I think it's a good add-on and I didn't want to deprive the pubic of its use. And I'll be honest, I hardly ever use it myself. I'm running the project as a public service -- I guess just because I'm a good guy.
I'm doing my best to hold it together. When we discovered Pale Moon I hoped it would let us live after FF deletes the XPCOM/XUL components which without our add-on won't work. I have no personal capability to change the code, I have no developers. I can change the install.rdf and add a block for Pale Moon, but as I said we are at our last revision. I'm not going to be updating our add-on if Pale Moon breaks it. The plain simple truth is we have no more capability to do anything except add new image hosts and fix broken image hosts. We won't be releasing a new version for every new version of Pale Moon. We won't be testing our add-on for every new version of Pale Moon because there is no sense in testing unless you have the option of fixing. If IHG quits working with Pale Moon then it is history and I can shut down the site. I'm sure we will lose Firefox before we lose Pale Moon.
So pretty much all of the facts above are not what I want them to be, but I have two choices. Try to get along with Pale Moon as long as our add-on is compatible. At such time as it becomes incompatible with both Pale Moon and Firefox my only choice is to shut down the website. I can do nothing more unless we are saved by a "white knight" who is an expert at JavaScript and PM/FF add-ons and wants to volunteer to BE our developer, and I don't see that happening.
All who read this are welcome to join our forum and discuss any issues you feel like discussing:
http://imagehost-grabber.org