I had someone else running 14.2 try and reproduce the issue but they were unable. I'm working on making more tests but its possible there is some kind of issue with the theme you are using causing the text to not show up, I mean is that a possibility, do you know?

It happens on all DE's that I try regardless of theme. The only other thing that I can think to try is to set up my i3 rig with 14.2 and try it there.

1 members found this post helpful.

Fuss is about PM devs not using/testing/supporting the popular extension.
A 'note to noscript users' on their forums was perfectly fine, blacklisting a working extension (for everyone) is not, IMO.

I use it since FF 2.0 because it can block all embedded media, and it can force many sites to use HTTPS (I wrote *.* in the HTTPS box)
FWIW it works fine here, noscript (5.1.8.5) and uBo legacy (1.16.4) on palemoon (27.9.1)

2 members found this post helpful.

I guess we both actually agree because I have the same versions you just listed.

Would this be the equivalent of using HTTPS Everywhere? Because if it does the same thing, I would love to have one less add-on.

2 members found this post helpful.

Compared to that, it lacks remote and 'cloud' capability, and it might take some time to list all the exceptions which don't have a cert.
But it's just 2 lines I guess, compared to a separate addon.

1 members found this post helpful.

I'm going to have to chalk it up to hardware incompatibilities? It works fine on my i3 rig. I have no idea why it is acting funny on my test rig. I'm going to do another clean install on it and try your 2018.05.06 build that I still have on it and see if I have the same issues with it. I guess that I'm going to have to test out Basilisk on it as well, but I have that installed on this (identical) rig and it works fine.

Thanks for the help khronosschoty.

Edit: Just for kicks, I loaded up Slackware64-current on my test rig, installed Pale Moon Beta and getting the same issues. There should be no reason why it does not work on that hardware.

1 members found this post helpful.

Let me know how it goes. Because if the latest Basilisk works then Pale Moon should as well. (A new Basilisk should be out soon if its not already out, that is the version I'm meaning). Furthermore if the older versions work that means there has to be a regression somewhere.

so I put Slackware64 14.2 live on an old barely working macbook I have sitting around and I booted up, and installed Pale Moon beta on there, the latest one I have uploaded and I'm not having any issues in about:config. I just wanted to share that.

1 members found this post helpful.

Your build that was marked as 2018.05.06 works normally. But, when I look at the 'About Pale Moon' is says 2018.05.12. I mean this is just a minor thing and has no effect on the function.

The new Basilisk in fact does NOT work normally for me. It is acting the same as your newest Pale Moon Beta builds for me.

Don't fret over this, I am sure that I wont be the only one that has issues.

1 members found this post helpful.

Ditto.

1 members found this post helpful.

27.9.2 (2018-05-18)
This is a security and stability update.

Changes/fixes:

We changed the language strings for softblocked items so people will cry less when we do our job.
(CVE-2018-5174) Prevent potential SmartScreen bypass on Windows 10.
(CVE-2018-5173) Fixed an issue in the Downloads panel improperly rendering some Unicode characters, allowing for the file name to be spoofed. This could be used to obscure the file extension of potentially executable files from user view in the panel.
(CVE-2018-5177) Fixed a vulnerability in the XSLT component leading to a buffer overflow and crash if it occurs.
(CVE-2018-5159) Fixed an integer overflow vulnerability in the Skia library resulting in possible out-of-bounds writes.
(CVE-2018-5154) Fixed a use-after-free vulnerability while enumerating attributes during SVG animations with clip paths.
(CVE-2018-5178) Fixed a buffer overflow during UTF8 to Unicode string conversion within JavaScript with extremely large amounts of data. This vulnerability requires the use of a malicious or vulnerable extension in order to occur.
Fixed several stability issues (crashes) and memory safety hazards.

2 members found this post helpful.

The fact that they think the problem was the wording is outright insulting. Not only are they dishonest, they are despicable too.

2 members found this post helpful.

I started to highlight that as well. I'm going to start experimenting with some new browsers.

Waterfox is a nice Firefox based browser. And Alex (dev) is not a douchenozzle as far as I can tell so far. That's probably where I'm going.