diff options
| author | mmenke <mmenke@chromium.org> | 2016-02-05 12:53:24 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-05 20:59:24 +0000 |
| commit | fdd4fc741f5797719784f46799051c31e50ce09f (patch) | |
| tree | e6386161a31b09d0d39c2778b9b648aebe12b19a /remoting/remoting_all.gyp | |
| parent | 7492a5fcb13ad3236e5251eb2ea0776c730e50b0 (diff) | |
| download | chromium_src-fdd4fc741f5797719784f46799051c31e50ce09f.zip chromium_src-fdd4fc741f5797719784f46799051c31e50ce09f.tar.gz chromium_src-fdd4fc741f5797719784f46799051c31e50ce09f.tar.bz2 | |
Remove ImportCookies from CookieMonster interface.
Consumers now use CookieStore::SetCookieWithDetailsAsync.
The old method grabbed a mutex and synchronously set all cookies. It's
the only cookie method that did that, and it's unclear why. With the
new code, the cookies won't be set until any old matching cookie has
already been loaded from the store, which will then be overwritten.
With the old code, that didn't happen, and it's unclear if the code
was actually correct.
This also adds an argument to SetCookieWithDetailsAsync:
last_access_time, to better match old behavior.
TBR=bauerb@chromium.org
BUG=579653
Review URL: https://codereview.chromium.org/1663473002
Cr-Commit-Position: refs/heads/master@{#373902}
Diffstat (limited to 'remoting/remoting_all.gyp')
0 files changed, 0 insertions, 0 deletions