Services/Sync/Addon Sync: Difference between revisions

m
Line 42: Line 42:
This is a complicated issue and the decision was driven mainly by privacy and security concerns.
This is a complicated issue and the decision was driven mainly by privacy and security concerns.


We understand that most users (possibly even an overwhelming majority of them) will want add-on sync to *just work* when they upgrade to a Firefox that supports it. However, there are a number of issues with this.
We understand that most users (possibly even an overwhelming majority of them) will want add-on sync to ''just work'' when they upgrade to a Firefox that supports it. However, there are a number of issues with this.


Most of the issues center around unexpected behavior when syncing add-ons for the first time. It is possible for an existing Sync user to unknowingly launch a Firefox version that supports add-on sync (where the previous version didn't). This could be due to silent Firefox updates, a system upgrade performed by an IT administrator, another user on the machine upgrading Firefox, etc. The first time this device synchronizes, it could pull down add-ons from another device (again, it is possible the other device had add-on sync configured unbeknownst to the user). There are a few issues here:
Most of the issues center around unexpected behavior when syncing add-ons for the first time. It is possible for an existing Sync user to unknowingly launch a Firefox version that supports add-on sync (where the previous version didn't). This could be due to silent Firefox updates, a system upgrade performed by an IT administrator, another user on the machine upgrading Firefox, etc. The first time this device synchronizes, it could pull down add-ons from another device (again, it is possible the other device had add-on sync configured unbeknownst to the user). There are a few issues here:
canmove, Confirmed users
409

edits