Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 4 antwoorden
  • 4 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van 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.

Gekozen oplossing

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

Dit antwoord in context lezen 👍 0

Alle antwoorden (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

Gekozen oplossing

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!