搜尋 Mozilla 技術支援網站

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

了解更多

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

  • 3 回覆
  • 1 有這個問題
  • 3 次檢視
  • 最近回覆由 Quarantain

more options

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.

被選擇的解決方法

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.

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

所有回覆 (3)

more options

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

more options

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 ?

more options

選擇的解決方法

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.