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