Spotify's account page is completely broken in Firefox
What other mainstream websites only work in Google Chrome?
The entire web sucks. It's not just Firefox and it's not just Spotify.
On Chrome Android if expand and then long press an image result I get the native menu that allows me to save the menu to my device.
On firefox android however, after expanding the image result I cannot long press the image. Instead, pressing the image shows a lighybox overlay and a button that links to the image result on the original webpage (and ofc it's always behind pinterest auth or something) and a "share" button that opens a popup that is certainly not the native Android share feature.
I'm convinced it's a deliberate action.
Each morning, I would sit at my desk, and press play in the browser tab that Spotify was running in. Nothing would happen. No music, no loading indicator. Just nothing.
Sometimes I could get Spotify to work by reloading the tab, but most often I'd have to destroy the tab and create an entire new one. Then the site would work again. I never investigated why. I have a job to do, and I just want the music player to work. I'm not reporting a bug in a consumer music service.
I tolerated this for about a year. One day, the annoyance just reached a breaking point. I cancelled my subscription and signed up with Google music.
I sympathize with the Spotify developers. Delivering software is a hard job, and I know that from experience. Delivering it to multiple runtimes is even harder. But here's the thing:
Google music works without issue in Firefox, just like all their other products. To me, that is standard of quality for web applications. Anything else is not good enough, and people shouldn't tolerate it.
I just looked at https://www.spotify.com/us/account/profile/ in my Firefox and it appears to be working just fine. Could you explain what's going wrong for you? What kind of issue are you seeing, and which browser/version/platform are you on?
In general, reporting such things to https://webcompat.com/ is a great idea, because that increases the chance of resolving the issue significantly!
The _main_ reason for this is that SDK providers (Google, Facebook, ...) give you sample code that will _break_ the entire page if blocked. Busy devs will simply copy paste that code and move on to the next project.
Firefox has a nice page explaining how to fix that but nobody seems to read it.
Chrome+safari is the new IE6.
It's like conspiracy to keep Firefox users out of all meetings.
(Or it's their subpar webrtc support, who knows)