Closed Bug 1274896 Opened 8 years ago Closed 8 years ago

Reset the Sync client on places autorestore

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1199077

People

(Reporter: markh, Unassigned)

Details

Split from bug 1230011 comment 5:

rnewman:
> I agree that on auto-recovery we should do a fresh sync to make 
> sure we didn't accidentally roll back by a week and 'miss' a 
> bunch of changes that we already saw. That's the approach we 
> take on iOS, too.

In terms of desktop Sync, "fresh sync" translates to Service.resetClient(), but not .wipeServer(), right?

So the 2 tasks here are:

* Work out some sane way for Places to let us know that an "auto restore" of bookmarks happened, and ensure that our existing "bookmarks-restore-success" observer does *not* kick in here (that's bug 1230011; user-initiated-restore and auto-restore get different treatment. Note that auto-restore almost certainly happens before Sync is initialized.

* Make the .resetClient() call when Sync initializes and it finds an auto restore was done.
Flags: needinfo?(rnewman)
Flags: firefox-backlog+
(In reply to Mark Hammond [:markh] from comment #0)

> In terms of desktop Sync, "fresh sync" translates to Service.resetClient(),
> but not .wipeServer(), right?

Yes, though only reset bookmarks and history. No point re-syncing passwords and prefs…


> So the 2 tasks here are:

Yup!
Flags: needinfo?(rnewman)
Triage: dupe of bug 1199077
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.