#2 Support for Pale Moon

Pale Moon is based on pre-australis Firefox code, and thus is incompatible with the current addon.

If possible, I would say that you could even submit a pull request to just include this into the core and they would likely add it to fix the bug.

Since this add-on doesn't touch UI at all, it doesn't matter whether Australis or not. However, Pale Moon currently doesn't seem to support ECMAScript 2015 Edition (ES6). Also, Pale Moon should include (without supporting Australis part) support for JPM-based add-ons. Many incompatible add-ons are just so because Pale Moon does not support JPM. (Just a mater of adding some CommonJS modules. No need to support Australis.)

That said, dirty port is available for now: https://notabug.org/neuemars/xpi-bucket/raw/master/palemoon/@no-resource-uri-leak-0.2.1-pm.xpi

This add-on serves its purpose as a short-term fix for users and a campaign to raise awareness of the problem among browser developers. Browser developers can develop a C++-level fix while we're using the add-on.

Pale Moon ticket: https://github.com/MoonchildProductions/Pale-Moon/issues/445

Tor Browser ticket: https://trac.torproject.org/projects/tor/ticket/8725

The dirty version works, thanks! Anyway i have problems with the about:home site now: XML-Verarbeitungsfehler: Nicht definierte Entität Adresse: jar:file:///C:/Program%20Files/Pale%20Moon/browser/omni.ja!/chrome/browser/content/browser/abouthome/aboutHome.xhtml Zeile Nr. 22, Spalte 12: -----------^

Maybe because the site have a search engine included. Hope this can be fixed.

Your dirty port for Pale Moon doesn't work with Pale Moon 27 (current alpa) It would be nice if your addon can be ported to work with Pale Moon 27.

The addon must not be a jetpack addon, since Pale Moon 27+ doesn't support jetpack addons.

Thanks for your work!

Link for Pale Moon 27: http://www.palemoon.org/WIP/

Agreed with @klausta. I like PM but this next breaking change is frustrating.

Your addon is now marked as incompatible because of Jetpack. Can you please make a build without Jetpack?

It depends on what you mean by "Jetpack" (if you are dropping CommonJS altogether, which itself is not Jetpack, that's a problem), and whether PM is going mutiprocess or not. Note that I don't have much free time for now, but I'd rather create an abstraction layer that just implements some features "missing" from PM if I could.

I tend to think PM's losing more and more 3rd party devs as they remove more essential features they just don't like. (For example, think of Alt-key no longer showing the menu bar, or many developer tools that just disappeared.) This is because most devs simply don't care much. That's why Mozilla's trying hard to make Chrome extensions compatible with their browser.

By the way, I'd like www.palemoon.org to stop using CloudFlare (it's just annoying).

I mean with Jetpack the Jetpack/add-on SDK which Pale Moon never support. The only change now is we users get a info if a addon can't be installed because it uses Jetpack SDK. The most addons doesn't use Jetpack.

A Pale Moon version would be very awesome! If you need help, you can ask in the Pale Moon forum too: https://forum.palemoon.org

Pale Moon get more devs instead of losing devs. The most addon devs make a Pale Moon version or even drop Firefox because of the way Mozilla go.

Pressing the Alt-key for menu bar works in all Pale Moon versions, since beginning. The developer tools never disappeared in Pale Moon. Pale Moon doesn't include all devtools like Firefox because no normal user want this- but Pale Moon 27 will change that.

I wonder if Mozilla will drop all own addons and only use Chrome extensions in future.

palemoon.org use CloudFlare only for accessibility in case of server problems and you should take a note about that. I never see any CloudFlare stuff in NoScript nor uMatrix. Are you a TOR user?

@neuemars It's broken in Pale Moon again. Is there another way to fix the bug or a chance that it could be made compatible again?