| commit | ec4bc5a8d03d09f4a86252b37b56250544f2172b | |
| author | jkarlin <jkarlin@chromium.org> | |
| Thu, 16 Jul 2015 11:10:04 +0000 (16 04:10 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 16 Jul 2015 11:11:02 +0000 (16 11:11 +0000) | ||
| tree | ba57eae4ce9031324fe9297889510baeb6314611 | treesnapshot (tar.gz zip) |
| parent | 962e17874344690d81f0e7d2171118b8207cad57 | commitdiff |
Reregistering a background sync should reset its state from failed to pending
A failed sync means it tried once and gave up. Reregistering that sync (without first unregistering it) should reset the state so that it can try again. This CL makes that change.
BUG=507309
Review URL: https://codereview.chromium.org/1226303007
Cr-Commit-Position: refs/heads/master@{#339012}
A failed sync means it tried once and gave up. Reregistering that sync (without first unregistering it) should reset the state so that it can try again. This CL makes that change.
BUG=507309
Review URL: https://codereview.chromium.org/1226303007
Cr-Commit-Position: refs/heads/master@{#339012}
| content/browser/background_sync/background_sync_manager.cc | diffblobblamehistory | |
| content/browser/background_sync/background_sync_manager_unittest.cc | diffblobblamehistory |