为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

How do I disable the Firefox 8.0 add-on compatibility assistant?

  • 2 个回答
  • 31 人有此问题
  • 2 次查看
  • 最后回复者为 wolfbeast71

more options

The new "add-on compatibility assistant" is nice for some users, but causes issues if you have internal distributions of the browser with included/bundled add-ons that should be accepted without question. These add-ons in the assistant are listed as third-party and unchecked by default, which is definitely not desired behavior.

How do I disable the assistant so it will use the "old" compatibility checker instead, even on first run after upgrading? Or is there a way to specifically list extensions that should be checked as "keep" by default or be hidden from the assistant?

The new "add-on compatibility assistant" is nice for some users, but causes issues if you have internal distributions of the browser with included/bundled add-ons that should be accepted without question. These add-ons in the assistant are listed as third-party and unchecked by default, which is definitely not desired behavior. How do I disable the assistant so it will use the "old" compatibility checker instead, even on first run after upgrading? Or is there a way to specifically list extensions that should be checked as "keep" by default or be hidden from the assistant?

所有回复 (2)

more options

extensions.checkCompatibility.8.0 boolean set to false. This should allow you to use any extension that is disabled.

more options

extensions.checkCompatibility.8.0 only disable the compatibility check - that is NOT what I asked :/ The assistant lists v8 compatible, bundled add-ons as being "third party" and they are not checked to keep by default. I don't want bundled add-ons that are supplied with the browser to show up - and if that can't be done, I want to completely disable the add-on assistant that is new in v8.

It has nothing to do with the add-ons not being compatible with v8.