Open Bug 645259 Opened 14 years ago Updated 3 years ago

Make preferences sync... sync

Categories

(Firefox :: Sync, defect, P3)

defect

Tracking

()

People

(Reporter: rnewman, Unassigned)

References

Details

(Whiteboard: [sync:prefs])

IRC: rnewman: philikon: am I crazy, or does our prefs engine not so much "sync" as treat all prefs as a single record? rnewman: from the looks of it, if you modify two different prefs on two different devices, whichever one syncs last has its change overwritten by the server record philikon: rnewman: correct This should be easy to verify: * Create two profiles, synced * Modify pref A on profile 1 * Modify pref B on profile 2 * Sync profile 1 * Sync profile 2. Profile 2 will have pref B set to its value from profile 1 -- i.e., the local change will be undone. If this is the case, it's an awful opportunity for bugs, particularly with our default fairly long sync intervals.
(In reply to comment #0) > If this is the case, it's an awful opportunity for bugs, particularly with our > default fairly long sync intervals. The idea is that when one of the prefs in question changes, we bump the score to a ridiculous amount to immediately force a sync on idle. Of course, that won't have the other machines download the new setting any more quickly, but smaller Sync intervals should help here. I also think we need more flexible ways for an engine to do reconciliation. In this case, the prefs engine could easily reconcile changes if two separate prefs were changed.
I think this is pretty well demonstrated by, e.g., Bug 656151. And we ought to do Bug 582536, too.
Depends on: 582536
Whiteboard: [needs verification] → [sync:prefs]
Flags: firefox-backlog+
Priority: -- → P3
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.