引言回覆:
This makes me sad. And it's a problem that's been magnified by the switch to rapid release. One of the strengths of Firefox is it's rich selection of add-ons. In fact, 85% of Firefox users have chosen to install an add-on. On average, those users have 5 add-ons installed. Firefox users really love their add-ons. So it's not surprising that they get frustrated when one of their favorite add-ons gets disabled because it's not marked as being compatible with the new Firefox update they just installed.
So I started working on a project to fix it. The end result will be that most add-ons will automatically be compatible with Firefox, starting with (hopefully) Firefox 10.
At the time of writing this, I've not yet finished the project. There are parts described below that I haven't completed yet. But it's progressed far enough to safely enable the new behavior on Nightly builds, starting with today's Nightly build (labelled 2011-11-18).
Many of the changes are also on Aurora, but disabled. If you want to test the new behavior, go into about:config and change the extensions.strictCompatibility preference to false (true to re-enable the old compatibility behavior). Once I have a couple more major bugs fixed, we'll make the call on whether to enable the new behavior by default on Aurora (which will ultimately become Firefox 10).
http://theunfocused.net/2011/11/19/solving-firefoxs-add-on-compatibility-problem/在目前的 Aurora 與 Nightly 新增了 extensions.strictCompatibility 這個值。
預設為 true,也就是目前舊版本的相容模式。
若值為 false,則將啟動新式的相容模式,也就是等於內建了 Add-on Compatibility Reporter 套件的相容模式,
是這樣子嗎?
預計11版將預設啟動,也就是值為 false,但是一但啟用,難道不會對 Firefox 穩定性造成影響嗎?