summaryrefslogtreecommitdiffstats
path: root/WATCHLISTS
diff options
context:
space:
mode:
authortim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-02 01:25:24 +0000
committertim@chromium.org <tim@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-02 01:25:24 +0000
commite0976a77dcc9be00485086b5b0e112fe6d159ff2 (patch)
tree31b070d0463f6bf48322e954a554ffe021dcba9b /WATCHLISTS
parente3aa42411afbb1c4973380f0dc79130b6780f910 (diff)
downloadchromium_src-e0976a77dcc9be00485086b5b0e112fe6d159ff2.zip
chromium_src-e0976a77dcc9be00485086b5b0e112fe6d159ff2.tar.gz
chromium_src-e0976a77dcc9be00485086b5b0e112fe6d159ff2.tar.bz2
Changes to web database and autofill components required
to sync profiles / addresses. The main part here is adding Refresh to the PersonalDataManager. It changes the expectation that the PDM is the only thing modifying autofill, which is necessary as the sync engine connects directly to the WebDatabase on the DB thread. The tricky part is ID generation, which I spent a great deal of time harping over in my sync change to make sure that everything is in an eventually consistent state. Note that because of the way the autofill window takes an isolated copy of the data, there *are* extremely rare cases where an edit will get dropped - I cover this case in PersonalDataManagerTest.Refresh. TEST=WebDataServiceTest, PersonalDataManagerTest. Review URL: http://codereview.chromium.org/1550007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@43426 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'WATCHLISTS')
0 files changed, 0 insertions, 0 deletions