搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 3 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 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.