diff options
| author | maxbogue <maxbogue@chromium.org> | 2016-03-11 10:47:10 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-11 18:48:27 +0000 |
| commit | 76b6100f27b728e8235746b14e4a8c784eae4549 (patch) | |
| tree | b27b99c4f85015addf5fc2e792a670f01c3f4a87 /components/sync_driver/sync_policy_handler.h | |
| parent | bc7a86115749939e239f9ec5bb775f0171620a8e (diff) | |
| download | chromium_src-76b6100f27b728e8235746b14e4a8c784eae4549.zip chromium_src-76b6100f27b728e8235746b14e4a8c784eae4549.tar.gz chromium_src-76b6100f27b728e8235746b14e4a8c784eae4549.tar.bz2 | |
[Sync] Simplify sync startup behavior.
Now IsFirstSetupComplete, IsSetupInProgress, and AUTO_START do not
directly factor into the sync startup logic. Instead, AUTO_START simply
sets IsFirstSetupComplete to true on signin, and sync datatypes can only
be configured if IsFirstSetupComplete && !IsSetupInProgress (aka the new
CanConfigureDataTypes helper function).
This change is motivated by wanting to have better understanding and
control over when and how sync starts up in order to fix the attached
bug.
BUG=462796
Review URL: https://codereview.chromium.org/1575153004
Cr-Commit-Position: refs/heads/master@{#380685}
Diffstat (limited to 'components/sync_driver/sync_policy_handler.h')
0 files changed, 0 insertions, 0 deletions