Pale Moon forum

Are there any release notes to the latest version of Moon Tester Tool (1.0.6)?

You can always look to commits log on GitHub. Latest changes were also mentioned here.

PS: I'm aware that some add-ons with old-style or uncommon install.rdf format (like Close tabs to the left or 2 Pane Bookmarks) can't be installed using Moon Tester Tool. The possibility to add support of such extensions is currently under investigation.

Moon Tester Tool has been updated to 1.1.0:

[±] Support old-style and uncommon install.rdf formats
[±] Description update
[+] Russian locale

JustOff wrote:Moon Tester Tool has been updated to 1.1.0:
[±] Support old-style and uncommon install.rdf formats

I tried to install Extension Options Menu 2.18 with Moon Tester Tool 1.10, but it refused to install it, returning the same error we were getting with Close Tabs to the Left, that it wasn't compatible with Pale Moon.

For comparison, I installed EOM 3.13 using MTT. Version 3.13 has a FF version number low enough to install in PM 27, but the toolbar button won't appear without modification to the chrome.manifest . MTT did add the necessary line to chrome.manifest (as the button appeared), so that's good news, but it obviously didn't modify the install.rdf because the listing still has the orange button in the Add-ons Manager.

(You may ask, why don't I just use Extension Preferences Menu? The main reason is that my favorite theme has a fully-themed toolbar button it uses for EOM, and it doesn't use it for EPM.)

gracious1 wrote:I tried to install Extension Options Menu 2.18 with Moon Tester Tool 1.10, but it refused to install it

Resolved in MTT 1.1.2:

[±] Support the non-standard RDF namespace

Hey! I upgraded to MTT 1.1.4, and got a big surprise! I went to AMO, and saw a big green "Add to Pale Moon" button! JustOff, have you considered including release notes?? You should announce when you add awesome features to your wares!
=^.^=

That was just a small cosmetic update, there is nothing to announce about it actually, but the changelog is always on GitHub.

JustOff wrote:That was just a small cosmetic update, there is nothing to announce about it actually, but the changelog is always on GitHub.

I mean something that shows up in the Available Updates view of Add-on Manager, like so:
You click on "Show Release Notes", and then you can see the notes before you update (or decide not to update).

Unfortunately Pale Moon Add-ons Site does not support release notes embedded into Add-ons Manager.

For those curious, the showing of release notes is on the roadmap at some point in the future:

https://github.com/Pale-Moon-Addons-Tea ... /issues/47

Just have forked your extension as Serpent Tester Tool - it make possible to install Pale Moon exclusive extensions on Basilisk (maybe also XUL Firefox or Waterfox!). To achieve this I do vice versa task of Moon Tester Tool - I change GUID in manifest from Pale Moon to Firefox. Of course, that won't make really incompatible extensions work, but it did the trick for me with, for example, Advanced Night Mode.

Here you can find it: https://github.com/Nebula-Mechanica/serpent-tester-tool
XPI file here: https://github.com/Nebula-Mechanica/ser ... l/releases



You did very cool job, JustOff, I enjoy using your extensions.

Moon Tester Tool has been updated to 2.0.1:

[+] Implement add-ons export and re-install in compat mode
[±] Move install trigger from options to AM utils menu
[-] Remove no more relevant css fix for Firefox themes
[±] Have install listener registered only when needed
[±] Improve support for uncommon install.rdf formats
[±] Properly handle manifest encoding
[+] Preserve original manifest data
[+] Add disclaimer and save warning
[±] Update description
[±] Code cleanup

Nice update, thank you.

I thought we were way past this tool's usefulness.

Moon Tester Tool has been updated to 2.1.0:

[+] Workaround false Australis detection in Pale Moon 29.0 and later

As a reminder, MTT is not a magic pill, and to ensure long-term compatibility, add-ons that were not designed for Pale Moon should be properly adapted and maintained.

I really wish you hadn't. This isn't helping anyone except masking compatibility problems and making the inevitable transition to Pale Moon extensions much harder than it has to be (which will likely damage browser adoption)

Maybe put it on the blocklist level 1 with escalation as progression dictates.

Moonchild wrote: ↑

2021-02-02, 12:22

I really wish you hadn't. This isn't helping anyone except masking compatibility problems and making the inevitable transition to Pale Moon extensions much harder than it has to be (which will likely damage browser adoption)

I am very sorry that you are viewing it from that angle. I believe MTT serves exactly the opposite purpose to what you stated. As far as possible downsides are concerned, it comes with a disclaimer that clearly explains its purpose and consequences of use.

Your intent is good but in practice people will just use this tool "to make their extensions work" and not for dev purposes, regardless of how much you state a disclaimer.
You know this too, there are plenty examples from past users to that effect.
So in what way is working around false Australis detection actually helping people test/develop anything? To me it really does seem like "just a workaround to make broken extensions not complain". Especially if your release is the day of the milestone release people will NEVER KNOW that more extensions need attention. Don't you understand that? Good intention, bad effect.