DigitalHomicide.ninja - Page doesn't load properly

[Tomaso]

Another one of those game giveaway sites that doesn't work with Pale Moon:
http://www.digitalhomicide.ninja/#!bundles/h319q/
Those white JavaScript boxes doesn't load at all.

Nothing I would actually use myself..
Just FYI.

..and yes, the page loads just fine with other browsers.

[Moonchild]

Another one of those game giveaway sites that probably uses the same framework that doesn't like our current lack of promises support.

[Tomaso]

Ah, I see.
Thanks for looking into it, Moonchild.

The list of sites that doesn't work with Pale Moon has gotten awfully long now..
I wonder how many of them are due to missing Promises support.
Guess I'll just have to recheck a bunch of sites once this feature is in place.

[trava90]

Have you tried using the ES6 Promises extension?

[Tomaso]

Have you tried using the ES6 Promises extension?

Tried it just now.
Didn't help.

[Moonchild]

The list of sites that doesn't work with Pale Moon has gotten awfully long now..

Actually, no, it hasn't. But it's easy to forget exactly how many site you visit that have absolutely no problem being displayed in Pale Moon.
There are a few frameworks that aren't very browser-agnostic, and those seem to be determining people's impression of Pale Moon's performance. I don't blame anyone for drawing that conclusion either, of course, since in general you'd want a browser that Just Works™ -- but considering we're a small independent browser, site owners are generally not going to give us the same attention as other browsers to make sure that it Just Works™ on the server side.

FTR: I never have to use a different browser for any of my browsing. The only time I use one is when I get a report of something not working, to verify if it is indeed Pale Moon.

We are all aware of the issues there are with Pale Moon and these frameworks and technologies that have been pushed into use (regularly way beyond what would organically be adopted by web designers); as far as promises is concerned, we even have a bounty listed for this. But, nobody wants to lend a hand. So, we'll be looking into solving these issues another way, to make the browser more compatible again.

[Moonchild]

Also, the error isn't Promises, by the looks of it. It's an invalid attempt at accessing DOM nodes:

Code: Select all

[16:25:29.917] Error: Permission denied to access property 'nodeType' @ https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:129
[16:25:29.917] "[Bugsnag] Ignoring cross-domain script error. See https://bugsnag.com/docs/notifiers/js/cors"
[16:25:30.128] Error: Permission denied to access property 'nodeType' @ https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:129
[16:25:30.128] "[Bugsnag] Ignoring cross-domain script error. See https://bugsnag.com/docs/notifiers/js/cors"
[16:25:30.218] Error: Permission denied to access property 'nodeType' @ https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:129
[16:25:30.218] "[Bugsnag] Ignoring cross-domain script error. See https://bugsnag.com/docs/notifiers/js/cors"
[16:25:31.663] Error: [$injector:modulerr] Failed to instantiate module App due to:
[$injector:modulerr] Failed to instantiate module App.controllers due to:
[$injector:nomod] Module 'App.controllers' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.2.29/$injector/nomod?p0=App.controllers
minErr/<@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
setupModuleLoader/</</<@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
ensure@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
setupModuleLoader/</<@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
loadModules/<@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
forEach@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105
loadModules@https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:10 @ https://js.gleam.io/assets/w-fc4572fb8e045ee0bba43669c39a4adb.js:105

This is a problem with AngularJS using bad CORS if not set up correctly.
(I think we've seen this gleam.io issue before on another site, exactly the same issue)

[Tomaso]

considering we're a small independent browser, site owners are generally not going to give us the same attention as other browsers to make sure that it Just Works™ on the server side.

Well, it wouldn't be that much of a problem, if the non-working pages only were obscure ones, like the one I reported in the first post here.
However, many of the sites that doesn't work in Pale Moon are some of the most commonly used ones in my region.
You've explained your inabillity to troubleshoot some of these sites, Moonchild, which can I understand.
..but the fact remains, that the sites in question just works flawlessly with every other browser that I've tried them with.
Like I've mentioned before, I actually had to stop recommending PM to other users because of these problems, cuz like you said yourself; most people want a browser that just works!

Anyway, I want you to know that Pale Moon is still my favorite browser, and I appreciate the incredible amount of work you've put into it!

btw; what's up with the 'Just Works' trademark label? :)

[Moonchild]

are some of the most commonly used ones in my region.

but the fact remains, that the sites in question just works flawlessly with every other browser that I've tried them with.

And I'm sorry to say that we can't magically "be exactly like the browsers your region seems to aim for". Not overnight anyway.

Maybe Norway's web sites in general trend towards frameworks that are incompatible with us -- which may be a sign that many are designed by a small group of web developers local to Norway. There really isn't much we can do otherwise than to try and work through it as best we can. if that doesn't meet the average requirements of your region's common websites, then you may simply be better off using a different browser until things change.

[half-moon]

considering we're a small independent browser, site owners are generally not going to give us the same attention as other browsers to make sure that it Just Works™ on the server side.

Well, it wouldn't be that much of a problem, if the non-working pages only were obscure ones, like the one I reported in the first post here.
However, many of the sites that doesn't work in Pale Moon are some of the most commonly used ones in my region.
You've explained your inabillity to troubleshoot some of these sites, Moonchild, which can I understand.
..but the fact remains, that the sites in question just works flawlessly with every other browser that I've tried them with.
Like I've mentioned before, I actually had to stop recommending PM to other users because of these problems, cuz like you said yourself; most people want a browser that just works!

Anyway, I want you to know that Pale Moon is still my favorite browser, and I appreciate the incredible amount of work you've put into it!

btw; what's up with the 'Just Works' trademark label?

Just because it works in other browsers, it doesn't mean that it is PM fault.

[Moonraker]

Not all browsers can display all websites.More often a bad website will cripple all browsers in some way.

[Tomaso]

Fixed in PM v27.0.0.a1. :)