Pale Moon forum

Ah I see. Well in this case I do think we need to rule out client-side issues first.

Crash fix will be in the next release.

I'm not sure I understand. What exactly should we be considering?

Confirmed, this is a crash in the DOM security check for ftp subresource loading.
You can work around it by disabling the crashing check: Set pref security.block_ftp_subresources to false.
Opened Issue #1710 (UXP) to track this.

Your hypothesis is poorly supported. That would only be the case if the default protocol in browsers has actually changed to be https instead of http (which to the best of my knowledge isn't the case). As for why the broken redirection might be less noticed, I guess that would be primarily due to th...

I'd have expected you to understand by now that the blocking extension itself does not do anything but provide a framework for blocking rules which are fully under your control. By definition, the blocking rules are never perfect due to necessary generalization (you can't supply and maintain a filte...

New Tobin Paradigm wrote: ↑

2021-01-09, 11:15

would people flock to me offering overwhelming adulation

They might? I'd expect you'd at least get a few thankyous because you'll allow continuation of their misconceptions around useragents on the web.

I mentioned this for a reason. Kendo: It would put everyone at ease if you could confirm what you are, in fact, doing with the browser. Officially-branded browsers are not your property to do with as you please and their redistribution is restricted. So far you've been rather opaque as to your exact...

Ultimate solution: Write your own Basilisk extension to set the global UA override. Considering the factual statement by Moonbat ( the sites' breakage is not an opinion , privacy is most definitely not helped by blanket overrides, and the "negativity" (rather relaying the negative consequence of so...

No issues here but it does look like you have unmaintained Firefox extensions in your profile. Try disabling those and see if the issue persists. Also, please post the output of help -> troubleshooting information... in your reply (use the copy as text button) so we have an overview of configuration...

Right, well if you need a browser for it then you're clearly not on an isolated network. But whatever your reasons for running XP, the main point of this thread is answered with a simple "no, it isn't", and the rest is just advice which you are clearly uninclined to listen to, so I'll call this topi...

Would probably also help if you check the developer tools -> browser console and see if there are any errors thrown there when you observe this behavior.

The error is in your language pack. You have to make sure that what you are trying to use has entries for all localized strings.
I'm not sure how you plan on troubleshooting that if the browser won't start, but good luck with it.

The code is in autorecovery.js

In fact I am still using Windows 98 to run software that would otherwise cost $3k to upgrade. You know that virtualization exists, right? upgrading the mechanics just to run a bloated version of Windows would cost a squillion. if you have that many vulnerable workstations, consider how much MORE it...

There is a reason you can easily make exception rules for websites that don't work with the filter sets supplied by default (or use a different subscription instead).

Good luck, anyway looking at Pale Moon's source code I'm almost sure that the root certificates recognized as EV are hard-coded in ExtendedValidation.cpp and there's no way to add your own without changing that file and making your own Pale Moon build. I'm not a Pale Moon developer, so confirmation...

That's actually not a bug, it's by design. Pale Moon has never included support for specific accessibility hardware, and if you need it to interface with e.g. a Braille rule then it may not work. If you are in need of that kind of accessibility functionality, then this browser is simply not a good m...

Without more information I can only -guess- that they are running into the safeguard we put in place to make sure that incompatible/broken language packs don't leave the user with an unusable browser (i.e. when the browser cannot initialize its main window). It will reset the locale to a known-good ...

Of course it hasn't.
But without telling us more, we can't help.

moonbat wrote: ↑

2021-01-08, 01:42

What telemetry and tracking code?

We never got around to do full dead code cleanup on that yet. Bigger fish and all that. None of it is functional though, just "still in the tree". It's akin to the many other cleanup tasks we still have that nobody helps with, like Android cleanup.