PaleMoon browser

[kfonda 25]

As of sometime on 12/26/15 the web client stopped showing in the PaleMoon browser. I just get a blank grey screen. I tried Chrome, IE, and Firefox and they all work as expected. I also tried a fresh install of PaleMoon on a different machine with the same grey screen. Does anyone have any suggestions for how I can fix it if it is on my end?

 

Here is the chunk of log from when I tried to load the page with PaleMoon.

2015-12-27 22:58:24.8719 Info App: HttpClientManager GET: http://192.168.1.81:49152/2/description.xml
2015-12-27 22:58:24.8789 Info App: HttpClientManager GET: http://169.254.5.216:49152/2/description.xml
2015-12-27 23:01:32.7463 Info HttpServer: HTTP GET http://media.compuwiz.com:8096/web/index.html. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.8) Gecko/20151126 Firefox/31.9 PaleMoon/25.8.1
2015-12-27 23:01:32.7473 Info HttpServer: HTTP Response 304 to 192.168.1.51. Time: 1ms. http://media.compuwiz.com:8096/web/index.html
2015-12-27 23:01:32.7903 Info HttpServer: HTTP GET http://media.compuwiz.com:8096/web/css/all.css?v=3.0.5839.38387. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.8) Gecko/20151126 Firefox/31.9 PaleMoon/25.8.1
2015-12-27 23:01:32.7903 Info HttpServer: HTTP Response 304 to 192.168.1.51. Time: 1ms. http://media.compuwiz.com:8096/web/css/all.css?v=3.0.5839.38387
2015-12-27 23:01:32.7943 Info HttpServer: HTTP GET http://media.compuwiz.com:8096/web/bower_components3.0.5839.38387/requirejs/require.js. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.8) Gecko/20151126 Firefox/31.9 PaleMoon/25.8.1
2015-12-27 23:01:32.7943 Info HttpServer: HTTP Response 304 to 192.168.1.51. Time: 1ms. http://media.compuwiz.com:8096/web/bower_components3.0.5839.38387/requirejs/require.js
2015-12-27 23:01:32.7943 Info HttpServer: HTTP GET http://media.compuwiz.com:8096/web/scripts/site.js?v=3.0.5839.38387. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.8) Gecko/20151126 Firefox/31.9 PaleMoon/25.8.1
2015-12-27 23:01:32.7943 Info HttpServer: HTTP Response 304 to 192.168.1.51. Time: 1ms. http://media.compuwiz.com:8096/web/scripts/site.js?v=3.0.5839.38387

[Luke 37113]

Palemoon isn't going to happen unless they update, sorry. It's based on Firefox but an old version - 31. I'm honestly surprised that it's been working at all. The web client is moving fast with new technologies that are only supported in the most recent 3-4 versions of each browser. 31 is just going too far back. I would ask them to update.

[kfonda 25]

PaleMoon is not an old version of Firefox, it was forked from Firefox a long time ago and has kept up with all of the latest tecnology. The latest version is less than a month old. I have not had any issues with any other websites other than the recent web client here.

 

Here is a clip from their website about this very issue:

Rumor: "Pale Moon is just a rebranded rebuild of an old Firefox version"
FALSE
Pale Moon has been on a divergent path with its own code for a long time already. It was a rebuild in 2009, yes. It was a rebuild with minor changes in the Firefox 4.0 era, yes. But we've come a very long way since then with an increasing amount of different code being carried over each time it was re-based on later Firefox code. It's a true fork now and has been employing rapid development (as opposed to rapid release) to solidify this independent direction with its own focus and attempt at keeping the browser sane, lean, and offering users choice and stability.
At the same time, Pale Moon's focus on security and evolving networking standards has added features and kept pace with those developments in other browsers, by e.g. adding TLS 1.1/1.2 support a while back, by offering OCSP-stapling, by keeping a close eye on encryption and the browser's security by continuing to port or re-implement security fixes that apply to Pale Moon as a browser. It is neither old nor outdated, it is not a "rebuild" and it does not use obsolete technologies or have security holes.

Here is a ling to their release notes if it helps: http://www.palemoon.org/releasenotes.shtml

 

Do you have any idea what it is that is not working so I can point them in the right direction?

 

I'm not trying to be a pain in the rear, I really do appreciate the work you guys have done and I have contributed to the cause. I also promote Emby online and offline everytime I get the opportunity.

[Luke 37113]

Thank you for your support.

 

I couldn't find what version of Firefox that it's based on, so I installed it and it reports Firefox 31 in it's user-agent string. So I'm not sure what to tell you. The latest version of Firefox is 43. Since they're based on Firefox, the version that it's based on is more important than the Palemoon version.

[kfonda 25]

I modified the Palemoon useragent string to return the same thing as Firefox 43 but I still get the same results. Every http request returns an 'HTTP Response 304'. Any suggestions or should I just give up.

[Luke 37113]

That basically just tells Palemoon to lie about the version of firefox which isn't going to solve anything. Firefox 31 was released in July 2014, so it doesn't look like keeping up to date is really one of their goals. I would ask them to update and use something else for now.

[kfonda 25]

As I said before, PaleMoon is up to date. If you would look at the link I posted above, you could see that they've been very active about keeping up to date with new technologies and security. The only reason they have Firfox in the uaser agent string is because too many websites rely solely on the UA string and refuse to recognize PaleMoon or any browser that is not from the top 3. Anyway, nevermind, I'll figure something out.

[Luke 37113]

Sorry, but it's not. I understand you want to defend your favorite browser, but it's behind the curve right now.

 

The user agent string doesn't just report firefox, it reports Firefox 31:

Firefox/31

The Promise API was added to Firefox in version 29 yet is not available in Palemoon:

 

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise

 

To quote their roadmap page:

 

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

With Pale Moon keeping front-end compatibility with v24 of Firefox, this is the API level that should be aimed for.

[kfonda 25]

Thanks for looking into it. I ended up installing the IE Tab 2 add-on and having it default the emby page to an IE tab. This solves the problem, at least for now. The reason I started using PaleMoon was because of the Australis change and the fact they they started issuing updates so often. Mozilla seemed determined to turn Firfox into Chrome. If I liked Chrome I would have just used Chrome, not the Firefox version of it.

[kbeck 28]

Thanks for starting this topic. I just installed Emby a few days ago and suddenly having problems today. Pale Moon worked fine a couple of days ago. Now I can't get to Metadata Manager. The flyout is completely blank and the Menu bar at the top is fixed to the screen location thile the thumbnails scroll past. At least I know how to get around it now.

 

 

KB