ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Twitter embeddings on webpages don't work.

  • 2 (ردّان اثنان)
  • 1 has this problem
  • 6 views
  • آخر ردّ كتبه taureanfighter

more options

For the longest time, anytime I read articles (like the screenshot image attached below via BuzzFeed), Twitter embeds don't come up, whether it be just texts or with images attached. It does, however, come up on Safe Mode. Is there any way I can alleviate this problem?

For the longest time, anytime I read articles (like the screenshot image attached below via BuzzFeed), Twitter embeds don't come up, whether it be just texts or with images attached. It does, however, come up on Safe Mode. Is there any way I can alleviate this problem?
Attached screenshots

All Replies (2)

more options

There are other things that need attention.

The System Details List shows that you have multiple Flash plugins.

  1. Shockwave Flash 18.0 r0
  2. Shockwave Flash 22.0 r0

You can find the installation path of all plugins on the about:plugins page.

You can check the Flash player installation folder for multiple Flash player plugins and remove older version(s) of the plugin (NPSWF32) and possibly (re)install the latest Flash player.

  • (32 bit Windows) C:\Windows\System32\Macromed\Flash\
  • (64 bit Windows) C:\Windows\SysWOW64\Macromed\Flash\

Make sure that your Avast security software isn't blocking this content.

If it works in Safe Mode and in normal mode with all extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) disabled then try to find which extension is causing the problem by enabling one extension at a time until the problem reappears.

Close and restart Firefox after each change via *"3-bar" menu button -> Exit (Power button)

  • Windows: File -> Exit
  • Mac: Firefox -> Quit Firefox
  • Linux: File -> Quit
more options

Well, I got rid of the Shockwave issue (which I had been trying to figure out how to solve for the longest, so thank you for that!).

After that problem didn't work, I then disabled Avast and that actually worked. So, it seems that the Avast extension is the problem here. Now, the question is should I keep the Avast extension disabled or is there a way around this problem that I simply have to check or uncheck a box for?