Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen
Gelöst Archiviert

Facebook games running Adobe Flash no longer respond properly.

ajp1228

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.

Alle Antworten (4)

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

Ausgewählte Lösung

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.

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.

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