Well, I'd suspect it's a site specific problem, as some of them only accept a known useragent string.
Try one of these:
Or windows useragent string for example:
The thing should go into prefs.js (but make sure the site specific override is enabled)
Should looks something like this for safeway:
If that doesn't fix, it's probably outside my scope, possibly a modern chrome feature that is required.
I don't use any sites with those kind of requirements, but I know they exist.

Had seen a few CSS contrast problems around though, usually solved by extensions, there's plenty of them on github.
For example "custom_css_for_fx_v2.2.9" *(I've had some luck with that one)

1 members found this post helpful.

@elcore,
Thanks for the suggestions!

Pale Moon 28.14.2 is now available.

https://www.palemoon.org/releasenotes.shtml

Pale Moon 28.15.0 is now available.

https://www.palemoon.org/releasenotes.shtml

This is a bit of a long shot, but just maybe someone else has run into it...

If I leave Palemoon running, but idle (window minimized, or just behind a bunch of other windows), it eventually freezes, and I have to kill the process. It never happens if I'm actively using Palemoon (typing up a LQ post, or just general clicking and scrolling).

This just started happening within the last couple weeks, around the time I upgraded to Palemoon 28.15.0. However, dropping back to 28.14.2 shows the same problem, so I don't think it's related to the Palemoon update.

I have one system running Slackware-current, and one one running Slackware 14.2 -- the freezes only happen on the Slackware-current machine. I've been applying updates pretty regularly, so it's presumably something that has been updated in Slackware-current in the last couple weeks.

I know this isn't much to go on -- but has anyone else seen anything similar?

1 members found this post helpful.

Before you consider pale moon browser, please consider that someone attempted to port it to OpenBSD in 2018 and was immediately confronted with "cease and desist" style language by a representative of the project, due to trademark usage (the project is licenced under MPL, but the binaries are released as "proprietary freeware" and the logo and name are trademarks).

This is the git repository and "cease and desist" demand, posted less than 24 hours after the forum thread was started, plus response from the person attempting the porting work and others: https://github.com/jasperla/openbsd-wip/issues/86

The thread by the individual porting the browser, requesting collaboration: https://forum.palemoon.org/viewtopic.php?p=134236

It's important to note:

a) Nothing ported to OpenBSD and available in ports, is officially part of the project. The project is the base OS and nothing more (this is true for FreeBSD and NetBSD as well). If the porter happens to be an OpenBSD developer as well, the port is still not part of the OS and not official. Pale Moon developers / contributors missed this point spectacularly and assume they were dealing with the "project". You will see multiple references which point to this. Project team members, simply don't care about some random 3rd party fork of a web browser in ports.

b) The individual concerned was not acting in any official capacity and was working as a private individual, in the "not for profit" (hobby) sense and most importantly posted on their forums to seek collaboration - less than 24 hours before the "take down" request - he was instead met with legal threats.

c) He was not "distributing" anything.

The irony is that the licence itself and the vast majority of the code is Mozilla's...

Disclaimer: I have no dog in this race. I dislike how Mozilla are operating in recent times, but I have never used pale moon, nor do I intend to - I simply believe that supposedly FOSS projects, using bully boy tactics, citing licensing restrictions, trademark law and issuing threats should be exposed, so that users can then make their decisions based on those facts.

Opinion: Based on the vile attitudes (worse than firefox style trademark enforcement) and enforced use of (patched) static libs (a large can of worms of potential security problems, which far outweighs any backported fixes from current firefox), obsolete Firefox codebase and lack of privilege separation and sandboxing, I wouldn't touch it with a ten foot pole...

Interesting, but nobody forced you to even consider it. There's a clear description of their target audience on their site, if you're not into it why bother even posting?
Sure the devs are willing and able to throw a tantrum, sometimes a bit over the top, but tell me 1 good reason to trust mozilla more.
Personally I trust mozilla even less, which is still a bit more than I trust anything with integrated CEF. So yeah, I guess it's your choice what to use and how.

1 members found this post helpful.

There is choice, that's not being disputed here, nor is this a matter of anyone being forced to consider anything / or not - and this not about "mozilla vs anyone" either. So I don't quite get your point in responding as you have either...?

Far from a "tantrum", they were being deliberately obnoxious.

You appear to be suggesting that valid criticism, with sources, should not be posted?

I seem to remember AlienBob refusing to provide a pre-built Pale Moon because of the community's hostility toward Slackware.

It's nothing new, it's gossip that is stale and out of date. I've already read about it in this very thread.

And I'm not sugggesting anything, just saying you're being salty over nothing since you're not even a user of their product.
And seriously, just because you have more trust and respect for nanny browsers such as firefox or chrome, it doesn't mean everyone should.

If you've read about their target userbase, you would know it's folks who liked netscape and firefox 2.0 and those that generally hate chrome and modern firefox.
It's folks who don't really care about the sort of thing you're being salty about, IMHO.

1 members found this post helpful.

I'm aware of the arguments against Pale Moon. For me, it's about tradeoffs. If there were a perfect browser, I'd use it. There's not, so I pick the least-bad one.

Firefox seemed to be going out of their way to annoy users for a while -- breaking plugins, refusing to allow user-selected home tabs, changing the interface on a monthly basis, forcing the Pocket thing on everyone, etc. I suppose I should give Firefox another try, especially since Pale Moon is starting to break on more and more web sites.

Just to be completely clear: this is all subjective, and those are my personal preferences. I'm sure that others have different preferences.

Anyway, it was my intent (back in post #590) to ask a technical question, not to start an advocacy war over web browsers. I'm still hoping someone might have a response to that.

Why not mention the OS version, binary package or source build, last known good browser version if any, and/or any form of terminal output?
We'd better just guess all these things, so here goes the standard; no I don't seem to have this problem, or at least I haven't seen it yet.

I mentioned most of that in my earlier post, but I'll add some more...

I'm running Slackware-current. On another system with Slackware 14.2, the problem does not occur. Both systems are uptodate with Slackware updates. The problem started occurring within the last ~2 weeks.

I'm using the binary palemoon package (the tarball from their web site). I'm running 28.15.0. I originally assumed the problem was in the latest palemoon, but downgrading to 28.14.2 shows the exact same problem.

I don't remember seeing any console output, but that's a good point -- I'll check again.

Ok, thanks. Are you running Slackware-current, with the latest updates? I'm trying to nail down a specific trigger for the problem.

No, I only target stable slackware-14.2 and slackware64-14.2 with unofficial source builds, for the most part kronos' scripts from SBo.
Other that that, I'm not affiliated.
And SBo is only tested for 14.2 so I guess if it works on 14.2 it's working as intended.
It could be anything though, from memory leak to kernel or power management, but probably something in the system is too new or something in the browser is too old.

I've been a big fan of Pale Moon, but, as you said, it has been "breaking" on more and more web sites. From the web site of a major supermarket chain to the local registrar of voters. Sometimes you can access a site, but do little else. Sometimes a site appears and then refuses to completely load the page. The biggest consistent problem has been not being able to see what I've typed into a box on the page, e.g., a search field.
When I run into trouble I'll try a different browser and between Firefox, Pale Moon and Vivaldi (a chrome clone) Firefox usually does the best job.