Black Screen on open.spotify.com

[Disil07]

Hello, I'm new here. Today I started to use Pale Moon, and yeah, it is nice . But, when I tried to open Spotify Web Player, it says: This browser isn't supported anymore". Then I tried to search if anyone had the same problem. Some people (here at PM forum) said that you need to edit your user agent in about:config. I did it, and after a few hours, I can now log-in to my Spotify account . Then I'm opening the web player it just show up as a black screen. Any advice on how to fix it?

Here is some technical Info:

Code: Select all

Operating system: Windows 10
Browser version: 29.1.1
32-bit or 64-bit?: 64-bit
Problem URL: https://open.spotify.com/
Theme: Default
Installed extensions: 
Name: Classic Add-ons Archive
Version: 2.0.3
Enabled: true
ID: ca-archive@Off.JustOff

Name: LiveClick Lunar
Version: 2.2.3
Enabled: true
ID: {7A86970F-5198-5370-9FCB-0EE0150876F7}

Name: uBlock Origin
Version: 1.16.4.28
Enabled: true
ID: uBlock0@raymondhill.net
Installed plugins: 
-AdobeAAMDetect
-Adobe Flash Player
-Silverlight Plug-in
-Java(TM) Platform SE 8 U231
-Java Deployment Toolkit 8.0.2310.11

[moonbat]

Console shows an error saying 'invalid regexp group', looks like they're using more of the new bullshit syntax added by Chrome.

[billmcct]

No errors on my 32 bit.

[Disil07]

No errors on my 32 bit.

Maybe it is because im using 64-bit browser? I guess something is wrong with my configuration, i dont know . Then how I can use spotify web player in PM? Should I use 32 bit version instead? Or anything else?

[coffeebreak]

See this thread on the same topic.
In future, please search the forum before opening a new thread.

The page renders fine if Native user agent mode is used.
To test: Preferenes -> Advanced -> General tab -> Compatibility, "User Agent Mode:" - and refresh the page.
For the longer term, you can set up a site specific UA override for spotify.com using Pale Moon's native UA string.

Edit:
But it seems you still need their app to play stuff.
Front page says: " This browser doesn't support Spotify Web Player. Switch browsers or download Spotify for your desktop."
When I click to "View on Spotify" it gives a similar message ", then after clicking to "Open Spotify", console error:

Code: Select all

Error: TypeError: e is undefined
Source File: https://open.scdn.co/cdn/build/open/open.42fbb199.js
Line: 1

[billmcct]

I think the problem is 64 bit or maybe Windows 10 specific. I am using 32 bit and "Firefox compatibility" mode on both Win 7 and 8.1 and Spotify renders correctly on both.

[coffeebreak]

I think the problem is 64 bit or maybe Windows 10 specific.

What's your user agent mode (or do you have a spotify SSUAO)?
(Please see my previous post, plus the one that's linked)

And can you use the web player?

[billmcct]

Well that's pretty damn strange. Was using "Firefox compatibility" and it played fine. Set PM to "native mode" to test it, and it gave the error "This browser doesn't support Spotify Web Player". Went back to "Firefox compatibility" and now it wont play any longer. Go figure.

[coffeebreak]

Well that's pretty damn strange. Was using "Firefox compatibility" and it played fine.

Concerninge rendering (not the player)...
Looking again, the SSUAO for spotify was in fact added to the dynamically updated built-in overrides several weeks ago, so it shouldn't matter which UA mode an individual set. Spotify should render for everyone.

Though the override doesn't seem to have updated, at least yet, in the portable testing version that I set up yesterday.
(\Bin\Palemoon\browser\ua-update.json contains no values, and spotify pages are still black for me with Compat mode)

[billmcct]

The screenshot above is in "Firefox compatibility" and "Native" rendered the same for me.

[coffeebreak]

The dynamically updated built-in override takes precedence over Compat or Native mode. Once it kicks in, spotify should always see your UA as Native regardless what UA mode is set.

For people who see a black page on spotify (when in Compat mode), the built-in override seems to be absent.

[billmcct]

My "ua-update.json" only shows:
{ }

[coffeebreak]

I only know that for me (and some other users, per earlier linked thread), Spotify renders when it sees a Native UA, but gives black pages when it sees the Compat UA.

The dynamic override implemented here is meant to make Spotify see a Native UA for everyone, regardless of UA mode, and I'm guessing it must be doing that for you somehow, if the site renders with Compat mode set. Though I don't know so well the mechanics.

(If that turns out to not be the case, I have no explanation and can only say that our experiences differ.)

[Disil07]

I only know that for me (and some other users, per earlier linked thread), Spotify renders when it sees a Native UA, but gives black pages when it sees the Compat UA.

Well that is strange. In my browser, Spotify render correctly when using "native" UA, but it says "not supported". But if I use Compatibility (Firefox or Gecko or manually tuning UA) it renders as a black screen. Nothing happened.

After a few hours of tweaking config, I get, well, nothing . I also tried to use "32-bit portable" PM, and yeah, it does the same results. Then how to fix it? I did not understand about "ua-update.json", so please explain it to me !

Actually I did open ua-update.json but yeah, i dont understand what is that because it is empty and only contain a blank parantheses "{ }". . Am I need to fill it with some kind of --code or anything else?

[Disil07]

Umm help me, I just click on a random button by accident, and now it says problem is solved . This issues is not solved yet! Please someone un-mark this post as solved

[Moonchild]

Off-topic:
Tip: Don't click on random buttons. especially when they have tooltip descriptions for what they do

[coffeebreak]

Well that is strange. In my browser, Spotify render correctly when using "native" UA, but it says "not supported". But if I use Compatibility (Firefox or Gecko or manually tuning UA) it renders as a black screen.

Edit:
But it seems you still need their app to play stuff.
Front page says: " This browser doesn't support Spotify Web Player. Switch browsers or download Spotify for your desktop."
When I click to "View on Spotify" it gives a similar message ", then after clicking to "Open Spotify", console error:

Code: Select all

Error: TypeError: e is undefined
Source File: https://open.scdn.co/cdn/build/open/open.42fbb199.js
Line: 1

There are two parts to the problem with Spotify:

- One is to make the page render. Showing them a Native UA fixes that.
(This should have happened automatically via a "dynamic UA override" (see previous posts), without needing to change UA modes, so I'm guessing there's a problem with dynamic overrides.)

- The second is to make the web player work. Unfortunately, AFAIK there is not currently a fix for the player.

... ua-update.json ... i dont understand what is that because it is empty and only contain a blank parantheses "{ }". :think:. Am I need to fill it ...?

No, do not touch it under any circumstances.
Editing it will fix nothing and could potentially cause major, hard-to-diagnose problems.

(I had thought it was supposed to contain all of the "dynamic UA overrides" that are sent to the browser from a palemoon.org server, though given billmcct's posts, maybe that's not so, or no longer so.)

[billmcct]

Well, I'm confused also. "open.spotify.com" and "spotify.com" renders the same in all three modes "Native, Gecko, and Firefox". Only now for me all three modes are stating the browser doesn't support the player.

[coffeebreak]

Well, I'm confused also. ...

What happens in a new profile?

[billmcct]

Renders correctly in "Native and Gecko", get a black screen in "Firefox comp".

EDIT:
Back in my regular profile and it renders correctly in all three modes. Go figure.