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

Search Support

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
Solved Wode archive me

Facebook container add-on does not work though installed and updated.

Quarantain

Windows 10 Pro, Firefox 60.0.1 (64-bit) - Quantum

I installed the Facebook Add-On, updated it to be on the safe side, logged off Facebook, closed FireFox, restarted FireFox and loaded the Facebook page. Despite a couple of attempts, I do not get the evidence that the container is in effect; i.e. facebook in blue and underlining.

Please help.

Windows 10 Pro, Firefox 60.0.1 (64-bit) - Quantum I installed the Facebook Add-On, updated it to be on the safe side, logged off Facebook, closed FireFox, restarted FireFox and loaded the Facebook page. Despite a couple of attempts, I do not get the evidence that the container is in effect; i.e. facebook in blue and underlining. Please help.
Xle ŋuɖoɖo sia le goya me

Ɖɔɖɔɖo si wotia

Thanks Pkshadow, the solution to the problem was indeed, temporarily disabling the Webroot Add-On. After the container got activated, I could re-enable the Webroot Add-on.

All Replies (3)

Hi, Mozilla only ok's Developers Extensions to work with Firefox. Support tries to help as much as possibly. You do need to read the page your downloaded from : https://addons.mozilla.org/en-US/firefox/addon/facebook-container/ as well as see the Developers Support page for help or info : https://github.com/mozilla/contain-facebook

Please check that Webroot Filtering is not causing the issue : SAFE MODE

In Firefox Safe mode these changes are effective:

  • all extensions are disabled (about:addons)
  • default theme is used (no persona)
  • userChrome.css and userContent.css are ignored (chrome folder)
  • default toolbar layout is used (file: localstore-safe.rdf)
  • Javascript JIT compilers are disabled (prefs: javascript.options.*jit)
  • hardware acceleration is disabled (Options > Advanced > General)
  • plugins are not affected
  • preferences are not affected

TEST''''is issue still there ?

Ɖɔɖɔɖo si wotia

Thanks Pkshadow, the solution to the problem was indeed, temporarily disabling the Webroot Add-On. After the container got activated, I could re-enable the Webroot Add-on.