Extensions.checkCompatibility: Difference between revisions
(→Background: warn about potential problems in intro) |
Alice Wyman (talk | contribs) (updated for SeaMonkey 2) |
||
| Line 8: | Line 8: | ||
Check extension compatibility on install and update. (Default) | Check extension compatibility on install and update. (Default) | ||
===false=== | ===false=== | ||
Do not check compatibility. Incompatible add-ons will be marked in the Add-ons Manager - its icon will have an exclamation mark over it and when the add-on is selected, the text | Do not check compatibility. Incompatible add-ons will be marked in the Add-ons Manager - its icon will have an exclamation mark over it and when the add-on is selected, the text ''Not compatible with <application and version>'' appears below the extension description. In addition, while the preference is set to false there will be an alert bar at the top of the Add-ons Manager saying that add-on compatibility checking is disabled and that you may have incompatible add-ons, with a button to re-enable it. | ||
==Caveats== | ==Caveats== | ||
| Line 18: | Line 18: | ||
==UI== | ==UI== | ||
===Mozilla Firefox 2.0=== | ===Mozilla Firefox 2.0 and above=== | ||
This preference can be toggled to true by clicking the button in the Add-ons Manager next to the “compatibility checking disabled” alert. (There is no way to set it back to false within the UI.) | This preference can be toggled to true by clicking the button in the Add-ons Manager next to the “compatibility checking disabled” alert. (There is no way to set it back to false within the UI.) | ||
''In other words, if you click on "Enable" you are not enabling extensions but enabling the compatibility checking and the flagged extensions will be disabled once more and not function. To Enable the disabled extensions you will have to start over by creating the configuration variable all over again.'' | |||
===SeaMonkey 2.0=== | |||
Same as above. | |||
==First checked in== | ==First checked in== | ||
| Line 31: | Line 33: | ||
* Firefox (all versions since 2.0b1) | * Firefox (all versions since 2.0b1) | ||
* Thunderbird (all versions since 2.0a1) | * Thunderbird (all versions since 2.0a1) | ||
* SeaMonkey (all versions since 2.0a1) | |||
==Related bugs== | ==Related bugs== | ||
Revision as of 18:05, 12 February 2009
Background
This preference allows disabling of extension compatibility checking. This is useful if you are using alpha, beta or nightly (development) builds which Add-on authors do not yet support. However, enabling incompatible extensions may cause crashes or other malfunctions.
Possible values and their effects
true
Check extension compatibility on install and update. (Default)
false
Do not check compatibility. Incompatible add-ons will be marked in the Add-ons Manager - its icon will have an exclamation mark over it and when the add-on is selected, the text Not compatible with <application and version> appears below the extension description. In addition, while the preference is set to false there will be an alert bar at the top of the Add-ons Manager saying that add-on compatibility checking is disabled and that you may have incompatible add-ons, with a button to re-enable it.
Caveats
- This preference does not exist by default.
- Installing an extension marked as incompatible with your application may cause your application to malfunction or crash.
- Disabling extension compatibility checking may cause your application to malfunction or crash after a future upgrade.
If disabling extension compatibility checking makes your application crash on startup, you should try starting in Safe Mode and re-enabling compatibility checking.
UI
Mozilla Firefox 2.0 and above
This preference can be toggled to true by clicking the button in the Add-ons Manager next to the “compatibility checking disabled” alert. (There is no way to set it back to false within the UI.) In other words, if you click on "Enable" you are not enabling extensions but enabling the compatibility checking and the flagged extensions will be disabled once more and not function. To Enable the disabled extensions you will have to start over by creating the configuration variable all over again.
SeaMonkey 2.0
Same as above.
First checked in
- Mozilla Firefox (trunk)
- 2006-05-29 by Rob Strong
- Mozilla Firefox (1.8 branch)
- 2006-06-05 by Rob Strong
Has an effect in
- Firefox (all versions since 2.0b1)
- Thunderbird (all versions since 2.0a1)
- SeaMonkey (all versions since 2.0a1)
