Seems like we hard code which things are disabled, so this causes inconsistencies with seamonkey which just reuses the firefox prefpane. So we would probably want to uncheck disabled engines too even though the pref might say checked.
The correct solution, imo, is to generate that UI dynamically based on which engines are registered and check/uncheck enabled ones. Perhaps with the addition that we can add a few hardcoded (disabled) ones, for the same reason they are there now--so that users know what might be in store for the future.
Summary: Disabled/checked state of engine sync list doesn't check registered engines → Engine sync prefs UI should be generated dynamically
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 493001
You need to log in before you can comment on or make changes to this bug.