搜尋 Mozilla 技術支援網站

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

了解更多

Facebook games running Adobe Flash no longer respond properly.

  • 4 回覆
  • 3 有這個問題
  • 3 次檢視
  • 最近回覆由 Oxylatium

more options

Last night I could no longer play Bejeweled Blitz, Solitaire Blitz, or other Adobe Flash player based games on Facebook using Firefox. The games load but do not respond correctly. I have to click twice on the page to get the view to update. However, these games work correctly in Internet Explorer. This started for me on the night of October 19. I tried four different Flash games tonight, some from different developers, and none of them worked correctly. I tested a Flash game on a site outside of Facebook, and it worked fine.

Last night I could no longer play Bejeweled Blitz, Solitaire Blitz, or other Adobe Flash player based games on Facebook using Firefox. The games load but do not respond correctly. I have to click twice on the page to get the view to update. However, these games work correctly in Internet Explorer. This started for me on the night of October 19. I tried four different Flash games tonight, some from different developers, and none of them worked correctly. I tested a Flash game on a site outside of Facebook, and it worked fine.

被選擇的解決方法

It's due to direct plugin drawing enabled in FF49. Type about:config in the location bar and set dom.ipc.plugins.asyncdrawing.enabled to false, then restart Firefox to apply.

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

所有回覆 (4)

more options

Update: I have now found that this problem is not limited to Facebook. Here is another game where I have to click twice before I can see what happened; this one also works correctly in Internet Explorer. http://www.pch.com/games/cards-solitaire/tri-peaks-solitaire/gameplay

more options

選擇的解決方法

It's due to direct plugin drawing enabled in FF49. Type about:config in the location bar and set dom.ipc.plugins.asyncdrawing.enabled to false, then restart Firefox to apply.

more options

Thank you! This seems to have fixed the problem! Firefox needs to correct this in future versions; I'm sure there are plenty of non-tech-savy users with the same problem who won't even try to find out what is wrong.

more options

For the record, regression bugs about this issue are related to bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1229961