Canmove, confirm
409
edits
Changes
no edit summary
TODO: Sync should catch all startup change types (the constants above) and react to them. We may need an API or some kind of verification/test to ensure newly-introduced startup changes/constants aren't missed by Sync. (This is all because getStartupChanges() takes a type as a parameter.)
Open Issues:
* What's the best way to reconcile installed add-ons with different Sync GUIDs? This will happen when two clients have installed the same add-on on different clients and then sets up Sync. The first Sync client will upload the records. Then, the 2nd will download that set and apply them. Should the Sync engine query AddonManager to see which add-ons (from the opaque *syncData* field) are not present or just call out into AddonManager and have it automagically recognize the dupe and update the Sync GUID? Either way, the Sync engine will need to know which Sync GUID disappeared so it can create a record saying the add-on was deleted/updated.
}}
{{FeatureInfo
