diff options
| author | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 00:27:18 +0000 |
|---|---|---|
| committer | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-24 00:27:18 +0000 |
| commit | ad76da7f13a8314f24e9acf9f43aae4fb6dfa6db (patch) | |
| tree | 1f66cd8d92a30d9da23d6e23231b74d75892d252 /chrome/test/selenium | |
| parent | cec1b8d4524bd0ce53a7b08b4263c788a5b6d72b (diff) | |
| download | chromium_src-ad76da7f13a8314f24e9acf9f43aae4fb6dfa6db.zip chromium_src-ad76da7f13a8314f24e9acf9f43aae4fb6dfa6db.tar.gz chromium_src-ad76da7f13a8314f24e9acf9f43aae4fb6dfa6db.tar.bz2 | |
Make it clear what last_sync_timestamp actually tracks. Update
last_sync_timestamp from the new_timestamp only, never from per-entry
timestamps. Use what the server sends us to know whether or not there
are more updates to fetch. Eliminate some unnecessarily complicated
logic having to do with the # of updates returned -- that's always a red
herring; with server-side filtering, it is indeed possible for 0 updates
to be returned along with a new timestamp.
BUG=37373
TEST=manual testing of 2 browser sync; unit tests.
Review URL: http://codereview.chromium.org/1161006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42413 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/test/selenium')
0 files changed, 0 insertions, 0 deletions