Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Is any work being done to render the google.com webpage the same as what's displayed from the stock android browser?

  • 4 wótegrona
  • 4 maju toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót buggystick

more options

The default UA for firefox mobile does not display the "better" mobile version (the one that is displayed in the stock android browser) of google's homepage. Setting the UA to android via the Phony extension results in a badly rendered page.

The default UA for firefox mobile does not display the "better" mobile version (the one that is displayed in the stock android browser) of google's homepage. Setting the UA to android via the Phony extension results in a badly rendered page.

Wubrane rozwězanje

I'm not entirely certain, but I wouldn't hesitate to acknowledge that suspicion. Similar behaviour is going on with the Google Plus website at the moment, and there is a bug on file to track layout issues wether it is a Fennec issue or a Google issue, at bug 668218

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (4)

more options

Hi Buggystick,

This would be an issue on Google's side, properly detecting our user agent and providing appropriate content. Setting the UA to Android via the Phony extension is the best workaround at the moment. I too, wish this were resolved, the Google sites offered to Fennec in comparison to the stock Android browser are garbage.

more options

I understand that Google is not properly detecting our UA string to provide appropriate content, but I'm still confused as to why firefox can't properly render the same sites as the Android stock browser when the UA string is changed. Are they using features only found in webkit?

more options

Wubrane rozwězanje

I'm not entirely certain, but I wouldn't hesitate to acknowledge that suspicion. Similar behaviour is going on with the Google Plus website at the moment, and there is a bug on file to track layout issues wether it is a Fennec issue or a Google issue, at bug 668218

more options

I imagine they are very related... I'm going to track that bug. Thanks!