Page 1 of 1

[INVALID] Jamendo not working

Posted: 2016-01-19, 08:46
by KNTRO
Both Pale Moon 25.8.1 & Pale Moon 26.0 L10N pre-release load —with default config— this Jamendo webpage but a few seconds later when it finishes loading it, the page turns blank.

Just in case, I already reported this to Jamendo and they told me they will forward this bug report to they IT division.

Re: Jamendo not working

Posted: 2016-01-19, 09:09
by dark_moon
So why you then post this in bug reports when its a website bug?

The site doesn't go for me black, but i have this in error console:
Error: TypeError: this.sessionObject is null
Source File: https://d3pcda6yi2m5ux.cloudfront.net/s ... 1268000.js
Line: 18

Re: Jamendo not working

Posted: 2016-01-19, 09:30
by KNTRO
dark_moon wrote:So why you then post this in bug reports when its a website bug?
Because I'm not techie, that's why I said Just in case. I don't know why Jamendo doesn't work with Pale Moon. It does with Internet Explorer 11, Microsoft Edge, Mozilla Firefox, Comodo IceDragon & SRWare Iron. Not with Pale Moon. So, a minor error in a line and Pale Moon can't deal with it? As I said, I just don't know, I'm just asking.
dark_moon wrote:The site doesn't go for me black
I didn't say black, I said blank. :mrgreen:
dark_moon wrote:i have this in error console:
Error: TypeError: this.sessionObject is null
Source File: https://d3pcda6yi2m5ux.cloudfront.net/s ... 1268000.js
Line: 18
So, this is the error. OK, reported it back to Jamendo.

Re: Jamendo not working

Posted: 2016-01-19, 11:32
by Moonchild
There's no error in the error console for me, but I do see the issue.
I gather it's a problem in their "onload" script tripping over something.

The web console does throw a bunch of specific framework errors:

Code: Select all

[12:27:22.123] "STARTING BOOTSTRAP"
[12:27:22.254] "dom finished loading..."
[12:27:22.254] "[ROUTER PLUGIN] initializeRouter"
[12:27:22.256] "[LIBRARY ROUTER] initializing ..."
[12:27:22.596] [object Object]
[12:27:22.596] [object Object]
[12:27:22.597] [object Object]
[12:27:22.597] [object Object]
[12:27:22.609] [object Object]
[12:27:22.734] [object Object]
[12:27:22.734] [object Object]
[12:27:22.845] [object Object]
And the object errors thrown have contents similar to:

Code: Select all

error: "View error"
name: "JamendoError"

OriginalErrorStack: "ie</t.error@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:3ie</t.tokenize@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:3ie</t.select@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:3t@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:2.find@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:3Z.fn.init@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:3Z@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:2h</t.prototype.template/s@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:8h</t.prototype.template/<@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:8n</e.prototype.then/s</a/<@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:5D@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1S@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1k@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1c@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1"
OriginalErrorType: "Error"

stack: "t@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:6h</t.prototype.render/r/<@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:8n</e.prototype.then/s</a/<@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:5D@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1S@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1k@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1b@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1c@https://d3pcda6yi2m5ux.cloudfront.net/scripts/main-build.1453197525000.js:1"

Re: Jamendo not working

Posted: 2016-01-19, 14:21
by KNTRO
My god…‼ Look at that mess, Jamendo‼ :P

So, dark_moon was right. This is not bug related to Pale Moon, but to this website. Now, I can't stop wonder why every other web browser I have installed here works just fine and Pale Moon, because of this issue can't work with the Jamendo website.
Off-topic:
Just my thoughts now
As I said, I'm not a code master, I'm simply an ignorant about coding, so from this ignorant point of view, what I say is not facts, but impressions. Having said that, I'd like to ask something to Moonchild: Pale Moon might be potentially much better coded than IceDragon or even Firefox! However, this may be like driving: Just because you have good driving skills, don't expect everyone else be as good as you are. So, you know this way better than me: a lot of banks and other multinational brands have websites which source codes are disgusting, and those sites are often far away from being even minimally functional. :mrgreen: So, I was thinking that all those false/null bug reports —just like this one by me— [you know what I mean, the classic This site doesn't work with Pale Moon, but works fine with Firefox] could be either because of user agent string sniffing or because of a few errors in the webpage's source code. Why other web browsers don't detect those bugs and the site still works? Don't you feel afraid of non technical people thinking Pale Moon is a bad browser when it actually detects those bugs in a page's source code? Because, ignorant people like me don't always understand these glitches and we —the ignorant ones— may think: Pale Moon is a bad web browser because this website simply doesn't work. So, my question is: Is it technically possible for Pale Moon to work "fine" with those ugly websites but also detects those sites' bugs? Because it seems like it's either one way or the other, not both. Feel a little worry about this, I must confess.
So, first thanks to dark_moon and then thank to you, MC, because with all these data I can feedback Jamendo folks hoping they read this thread and take necessary steps to fix their website.

Thank you for your time, guys. I really appreciate your patience and technical knowledge. Thanks for "translating" this for me. :thumbup:

I will add a prefix to this thread's title. Please, edit it if needed.

Re: [INVALID] Jamendo not working

Posted: 2016-01-19, 16:04
by megaman
Hubieras buscado, hermano. :)
viewtopic.php?f=3&t=10329&p=71484

Re: [INVALID] Jamendo not working

Posted: 2016-01-19, 17:48
by Moonchild
XD i thought it looked familiar.