Closed
Bug 868545
Opened 12 years ago
Closed 12 years ago
Don't sync early in startup
Categories
(Firefox for Metro Graveyard :: Sync, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 23
People
(Reporter: jimm, Assigned: jimm)
References
Details
Attachments
(1 file)
5.36 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
We should avoid triggering sync early in startup. RemoteTabs is currently doing this.
Assignee | ||
Comment 1•12 years ago
|
||
Assignee: nobody → jmathies
Attachment #745297 -
Flags: review?(mbrubeck)
Comment 2•12 years ago
|
||
Comment on attachment 745297 [details] [diff] [review]
fix
Review of attachment 745297 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/metro/profile/metro.js
@@ -422,5 @@
>
> #ifdef MOZ_SERVICES_SYNC
> // sync service
> pref("services.sync.registerEngines", "Tab,Bookmarks,Form,History,Password,Prefs");
> -pref("services.sync.autoconnectDelay", 5);
Was this not working? I notice that Metro is the only user of this pref; if it's broken or unused perhaps we should file a separate bug to remove the /services code for it.
Attachment #745297 -
Flags: review?(mbrubeck) → review+
Comment 3•12 years ago
|
||
It doesn't look broken to me, but note that this is equivalent to just calling scheduleNextSync() with appropriate values after a delay. It means "please automatically connect after this delay", not "please make sure we don't sync until this timeout has passed".
It doesn't stop other code from syncing before then, which is what was happening.
Assignee | ||
Comment 4•12 years ago
|
||
It didn't seem to be working, which is why I did the manual call and removed the pref. I'll file a follow up on it.
Comment 5•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 23
You need to log in
before you can comment on or make changes to this bug.
Description
•