為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

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

了解更多

Battlelog (for battlefield 3) does not work with Firefox 15.0.1. It works fine with the older Firefox 14.0.1

  • 1 回覆
  • 14 有這個問題
  • 7 次檢視
  • 最近回覆由 John99

more options

The flash features on the Battlefield 3 site - battlelog.battlefield.com do not work when Firefox updates itself to 15.0.1 It does not load the pages correctly or does it let you select/ click on anything in the flash parts. When I uninstalled 15.0.1 and reinstalled Firefox 14.0.1 I unchecked the option to let firefox re-upgrade itself and battlelog works fine.

The flash features on the Battlefield 3 site - battlelog.battlefield.com do not work when Firefox updates itself to 15.0.1 It does not load the pages correctly or does it let you select/ click on anything in the flash parts. When I uninstalled 15.0.1 and reinstalled Firefox 14.0.1 I unchecked the option to let firefox re-upgrade itself and battlelog works fine.

所有回覆 (1)

more options

I do not wish you to break Firefox on Battelfield 3, but have you tried using the latest version of Flash Player. You should also remember that using outdated versions of Firefox increases security risks to your computer and personal data.

You may get an answer to this sort of question faster by asking on a forum related to that game site, (and if you do please post back with the solution preferably with a link).

Possibly you could consider using Firefox 15 and later as the day to day browser, and Firefox 14 only for the problem games.

  • The simplest way to do that may be to install Firefox portable (I assume that will run a Firefox 14 version)
  • A better way would be to install multiple versions of Firefox. That is often considered advanced, but I imagine most experienced computer users could do it easily (I can provide links to instructions). That has the advantage that the problem could be looked at a bit more closely, possibly even filing a bug if it appears to be a Firefox regression causing the problem.