this post was submitted on 09 Jan 2024
40 points (93.5% liked)

Firefox

17740 readers
5 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
k_o_t@lemmy.ml
40
Google Search bug shows blank page in Firefox for Android (www.bleepingcomputer.com)
submitted 9 months ago by Elephant0991@lemmy.bleh.au to c/firefox@lemmy.ml
15 comments fedilink hide all child comments
 

The issue:

Android users with Firefox can't access Google Search (including intl sites and localized domains like google.de, .co.uk, .com.br). Instead, they see a blank page.

Cause:

A server-side bug on Google's end related to User-Agent (UA) sniffing, which serves an empty page to newer Firefox versions.

Affected versions:

All Firefox versions on Android (>= 65) including Mobile 121.0, Nightly 123, and older.

Chrome not affected:

The bug is specific to Firefox.

Solutions:

  • Use a different browser (Chrome, etc.) or search engine (DuckDuckGo).

Advanced users can:

  • Change Firefox's UA in developer settings or with add-ons.

  • Request the desktop version of Google from Firefox settings (region-dependent).

Status:

  • Problem identified as critical and escalated.
  • Still unresolved at the time of reporting.

Additional notes:

  • Disabling Firefox's Enhanced Tracking Protection doesn't fix the issue.
  • Some users report google.co.in loading the desktop site instead of mobile.
all 17 comments
sorted by: hot top controversial new old
[–] eya@lemmy.dbzer0.com 23 points 9 months ago (2 children)

"bug" aka purposely making firefox unusable on one of the largest websites in the world so more people use chromium

(these allegations are based solely on prejudice against google and its subsidiaries, and do not necessarily hold true in reality)

[–] OpenStars@startrek.website 5 points 9 months ago

Google:

Oh no anyway

[–] cyborganism@lemmy.ca 3 points 9 months ago* (last edited 9 months ago) (1 children)

Even if it's for only a short period of time, it's enough to do a lot of damage. Especially as people are becoming privacy conscious and are looking to start using Firefox.

[–] JokeDeity@lemm.ee 0 points 9 months ago (1 children)

What does this mean, I'm confused?

[–] cyborganism@lemmy.ca 1 points 9 months ago (1 children)

Yes. So was I when I wrote this comment. I don't know why I wrote Chrome.... 😑

[–] JokeDeity@lemm.ee 2 points 9 months ago

Makes way more sense now, lol.

[–] nieceandtows@programming.dev 6 points 9 months ago (1 children)

I tried signing into Google today on Firefox and got 'sigin in using a safe browser. This is not a safe browser'. I refreshed the page and it was gone and I was able to sign in. What the heck.

[–] joyjoy@lemm.ee 4 points 9 months ago

Google should follow their own advice and kill the user agent.

[–] JokeDeity@lemm.ee 6 points 9 months ago (1 children)

I really don't understand why Google isn't being taken to court over the obvious monopolistic strategies they've been implementing.

[–] Earring7377@mastodon.social 3 points 9 months ago

@JokeDeity they are in court right now with the USA.

[–] Scary_le_Poo@beehaw.org 3 points 9 months ago

Or you know, Don't use fucking Google?

Nowadays Google sucks ass anyway

[–] 1984@lemmy.today 2 points 9 months ago* (last edited 9 months ago)

Real professional engineers at Google. Reading the browser name is just so hard.

[–] omxxi@feddit.de 2 points 9 months ago

ah yes, a "bug"

[–] skizzles@lemmy.ml 2 points 9 months ago (1 children)

I'm on 121.0 mobile and have no issues accessing Google.com. Not that I use it anyway but figured I'd test.

[–] Lanky_Pomegranate530@midwest.social 1 points 7 months ago

It's not a bug. It's a feature.