Welp, guess I'm going to hell
Welp, guess I'm going to hell
49 comments
-
-
Guess I’m continuing to use Firefox in hell then
-
Join the club!
-
-
"It seems you have an ad blocker enabled. In order the enjoy the full benefits of heaven, please disable it and accept our cookies"
-
bro who is selling ads in heaven
-
Google Adsense has a further reach that you think
-
-
-
Hell runs on Linux so it never freezes.
-
It all makes so much sense now haha!
-
-
At least God isn't a crypto bro
-
Hell only supports IE. You hang out in limbo with all the cool kids.
-
If Firefox could run full screen video without crashing every fucking time ... that'd be great
-
I don't seem to have any problem with Firefox videos, maybe it's on your end
-
That's absolutely part of it. I have an old phone, but Chrome has been flawless on every phone I've had including this one.
-
-
49 comments
changes useragent to Chrome. Everything works perfectly on the site
Hmm. Interesting.
This is actually exactly how user agents evolved.
Chrome pretends to be safari.
IE pretends to be Netscape.
Safari pretends to be Firefox.
All popular browsers pretend to be at least one other browser for compatibility.
https://humanwhocodes.com/blog/2010/01/12/history-of-the-user-agent-string/
So it’s kind of like back in the Netscape days.
Men are men, women are men, boys are men, and little girls are FBI agents.
Stroking intensifies
My SO just had something similar pop up yesterday. She was running into weird errors on her Chromebook, so I had her change her user agent to Chrome on Windows. Everything magically worked. Hmm…
Which proves that M$ Teams definitely isn't heaven, because some things actually don't work with Firefox, as I recall.
Last time I tried to log in it said something about cookies and I had to use chrome.
that's your own fault for using teams though
also they don't count since Microsoft changes all links to force open in Edge and there's nothing you can do about it.
Calls don't work.
I does video meetings perfectly well. But not calls. And if you never used Teams, just try to guess the difference.
Doesn't solve the problem tho, which makes editing the useragent nothing but a temporary solution not worth being smartass-megamind about
What is the perceived problem, then? 99% of sites these days are all built with kits that support Firefox just as well as Chromium, the dev choice to not support or intentionally lock out Firefox is either just laziness (not wanting to deal with any potential problems or not given enough time to run full Firefox user tests) or incentive driven (middle manager has word from high manager that they can't support firefox because highest manager makes bank from Chromium).
The technical limitation isn't actually there in the modern web, it's almost always a manufactured limitation. I think I've only ever encountered a single website that didn't actually technically work on Firefox, and that was Weather Underground. Which they ended up fixing after 3 months or so.