본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 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.