搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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

  • 4 回覆
  • 4 有這個問題
  • 1 次檢視
  • 最近回覆由 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.

被選擇的解決方法

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

從原來的回覆中察看解決方案 👍 0

所有回覆 (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

選擇的解決方法

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!