Services/Sync/Features/Addon Sync: Difference between revisions

Services/Sync/Features/Addon Sync (view source)

737 bytes removed , 2 September 2011

m

remove old requirements section

canmove, Confirmed users

409

edits

@@ Line 51: / Line 51: @@
 ;Not sure about the update case
-;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.
 |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.