Canmove, confirm
409
edits
Changes
m
;LEFT THESE USE CASES HERE TO MAKE SURE I COVERED EVERYTHING
; Install propagation : User installs an add-on on one browser. When a sync occurs, this add-on record is uploaded to the Sync server. When another browser in the Sync profile connects, the add-on is installed automatically.
; Uninstall propagation : This is the same as install propagation except for uninstalls. An uninstall on one client will trigger an uninstall on another.
; User enabled state propagation : User opens add-on manager and disables an add-on. Sync will propagate this change to other clients. Ditto for enabling.
; Update propagation : User updates an add-on on one machine. Sync notices the update and schedules other clients to look for an update.
remove old requirements section
;Not sure about the update case
|Feature dependencies=; Sync GUID added to XPI Provider : Sync requires non-deterministic IDs to be affiliated with synchronized records. XPI add-ons currently don't have a suitable ID so once will need to be created.
|Feature requirements=*When a user installs an add-on, the add-on will be installed on all the user's devices connected with Sync.
