Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 4 respostas
  • 4 têm este problema
  • 4 visualizações
  • Última resposta de 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.

Solução escolhida

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

Ler esta resposta 👍 0

Todas as respostas (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

Solução escolhida

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!