Interesting, but when I go to the URL, above, by telling Pale Moon to open it in another tab, it displays as it always has in Pale Moon, i.e., without the list of currencies and their exchange rates.

Probably because the FF coders are more lenient.

Anyway the culprit is clearly the web page's coder, not the rendering engine's coder, so using this example to compare the respective merits of FF and PM is very moot.

1 members found this post helpful.

I'm not experiencing the issues with :
https://www.phoronix.com/scan.php?page=home and https://www.wsj.com/public/page/news...s-trading.html

I am using the Pale Moon script found here https://slackbuilds.org/repository/1...work/PaleMoon/ and the building and using gcc-4.9.4 found using the script found here https://slackbuilds.org/repository/1.../gcclegacy494/

and the packages I built can be found here http://repo.khronosschoty.org/Slackware/

It is all still very much a work in progress but I plan to support / maintain this for as long as I am able, and I aim that to be for a very long time.

I just want to point out that clang is not officially supported yet. Work on supporting more modern compilers, is I am I told, something desirable, but not currently at the top of their priorities list. I suspect the issues being reported, concerning said sites, is linked to unsupported compilation method, used to create the Pale Moon packages in question.

I also want to further note, I saw the picture of how "https://www.wsj.com/public/page/news-currency-currencies-trading.html" is supposed to to look when rendered correctly, however, my Fire Fox is not rendering the page any different than Pale Moon appears to be rendering it (I can't tell a difference).

Edit: for the record I used Slackware64-current to run these tests, the packages in question were compiled on Slackware64-14.2, and the Fire Fox I used to compare is the default one provided in the Slackware64-current package tree. I did these tests on a totally new user (and therefore totally new profiles etc).

3 members found this post helpful.

That Wall street Journal page looks exactly the same in Chromium, Firefox and Pale Moon - i.e. it does not show currency information in any browser.
However that second URL http://www.wsj.com/public/page/news-...s-trading.html shows currency information in all three - in exactly the same way.

And I am using the Pale Moon package from my own repository, not Khronosschoty's version.

2 members found this post helpful.

I just want to post here that, I've never had an issue with Alien Bob's package, whenever, I've tested it in the past. (I did not, however, test his package, with the websites being reported here as problematic.)

Au contaire, the image from post #86, above, was taken while using Firefox-ESR-52.2.0.

OTOH, it does not display in Vivaldi-1.9.818.50 or Pale Moon-27.2.1 or 27.3.0.

Edit in: Just installed Firefox-54.0, and it also displays the currency page correctly. Ditto, the "old" Opera-12.16. I like the display better in the "old" Opera than in Firefox.

1 members found this post helpful.

Yesterday Wall street Journal site did not display currency right in Pale Moon but ok in Firefox, but today its show just fine in both. I did install the latest ffmpeg 3.3.2, not sure if that made any difference.

2 members found this post helpful.

Its about time, I know I wasn't the only one having this issue. Like I said earlier, whats fast to some might be slow to others and vice-verse.

3 members found this post helpful.

I agree, this is all relative and hardware dependent. But you often see support threads like this one for example: https://redd.it/6qii46
Where the top comment says:
Which is FUD because the user test case is obviously firefox on mswindows with mswindows driver which use hardware acceleration and possibly a GPU co-processor.
On my machine, both VP8 and VP9 are way less demanding than H.264 blob.

And further down the line, a fedora user point of view:
Which is a lie, it's only unavailable in firefox and Linux kernel has nothing to do with it. Firefox devs intentionally chose not to support it.
It's available in mplayer on Linux, through ffmpeg and libvdpau on nvidia hardware. It used to be available through mplayer-plugin too, which is now deprecated because again:
Firefox devs chose not to support it, for reasons unknown.

This is all my personal opinion though, but ever since firefox-os was discontinued I suspect the devs just merged chrome and all that emulation code into firefox browser.
So now, instead of having a lightweight modular Phoenix browser like we used to, we've got to emulate their insecure-by-design OS platform to continue using their browser module on top of it.
VM's not really a browser, and I guess we're lucky there are still a few native browser projects around.

Wow. It's been awhile since I last looked in on this thread, and frankly, I am surprised by the number of responses I got.

It looks like people have different feelings regarding Palemoon vs. Firefox. To be honest, I wrote the OP in a moment of frustration with Firefox, which I have since resolved to my satisfaction (I use the latest version, which I package myself, instead of using the ESR version).

OTOH, chromium was beginning to become a real pain in my arse, what with spawning multiple processes and chomping up gobs of RAM. I have plenty to go around, but chromium's appetite for memory made it fat and slow, not to mention that when I wanted to shut down my system, it took forever to do so because of my system having to terminate chromium's multiple processes, as opposed to Palemoon & Firefox. (And yes, I run both at the same time, as each uses its own profile, and does not mess with the other's).

My solution to the problem was to uninstall chromium and just use Palemoon & Firefox. Shutdown is much faster, and memory is conserved during system uptime. I'm pleased with the current setup.

Just for the record, YouTube videos play just fine in Palemoon, without any choppiness.

4 members found this post helpful.

Hi,

New Pale Moon user here.
I'm happily running PM for couple of weeks now and everything works as expected.
(Although I'm not using Web heavily, in nowadays standards).

My killer feature is UI. Previously, I had to install add-ons and modify the look of Firefox until it was acceptable.
With Pale Moon, it's just the way I want it.

Some notes:
1. If you compile Pale Moon from source, I advise to use gcclegacy494. Using other compilers, I had experienced often crashes.
2. I built Firefox 54.0.1 from source using Slackware SlackBuild. But it was dead slow when starting up (more than 5 seconds to show up). Applying different compiler optimisations, solved the problem. I used the flags used in PaleMoon.SlackBuild:
--
Best regards,
Andrzej Telszewski

5 members found this post helpful.

Thanks, but I have used different versions and compiled my own. The problems was in the code and they apparently fixed it. I haven't tried the new version yet, been away from the comp.

I've no time to dissect it right now, but I assume it's these files you want to look into:

2 members found this post helpful.

Hi,

I too don't like the profile directory name.
But then, it's an already established name.
I decided not to fiddle with it, in order not to break something and cause me headaches ;-)

--
Best regards,
Andrzej Telszewski

Thanks for the hint. I don't really care about it myself, though. I was just trying to find it to help the other people who were asking about it. Actually, I'm not even using Pale Moon anymore.