Closed Bug 1594983 Opened 6 years ago Closed 4 years ago

Changing engines to sync doesn't force an immediate sync.

Categories

(Firefox :: Sync, defect, P2)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: markh, Assigned: markh)

Details

(Keywords: regression)

If you enable or disable an engine to sync, it should perform a sync immediately. Possibly a regression from one of the decouple bugs.

This sounds like bug 1584258, IIUC?

(In reply to :Lina Cambridge from comment #1)

This sounds like bug 1584258, IIUC?

Yeah, thanks. So this isn't a regression, has never been reported outside the context of sync-fest, and the current behaviour works better in the case of accidental mis-clicks (where you get a chance to "undo" the mis-click without needing to reupload everything). This wouldn't have even been reported if I didn't mis-remember that it was a regression and nobody put the case forward that bug 1584258 shouldn't be WONTFIX

So I'm inclined to WONTFIX this one too (or more likely, just dupe against bug 1584258 but leave that one as WONTFIX) - thoughts?

From Triage: We should initiate syncing after a user saves preference changes.

Priority: -- → P2
Assignee: nobody → markh
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.