diff options
| author | zea@chromium.org <zea@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-16 08:49:23 +0000 |
|---|---|---|
| committer | zea@chromium.org <zea@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-16 08:49:23 +0000 |
| commit | 490ce272373096bc50d43e5e5b814f291b245d21 (patch) | |
| tree | caf609ae6a0e3d3e9d52321b5725a51c336e946c /printing/image.cc | |
| parent | 3f22b6a1690dd5a8122548448c35c6e6df17fff2 (diff) | |
| download | chromium_src-490ce272373096bc50d43e5e5b814f291b245d21.zip chromium_src-490ce272373096bc50d43e5e5b814f291b245d21.tar.gz chromium_src-490ce272373096bc50d43e5e5b814f291b245d21.tar.bz2 | |
[Sync] Don't attempt an implicit passphrase if we know there's an explicit
SetPassphrase will no longer call into the backend an implicit passphrase if
there is already an explicit passphrase set. This prevents us from accidentally
thinking we have a passphrase error since failing to set a passphrase results
in SET_PASSPHRASE_FAILE being set as the passphrase required reason.
A follow-up CL will change the passphrase behavior to remove SET_PASSPHRASE_FAILED
BUG=118240
TEST=
Review URL: http://codereview.chromium.org/9700037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127129 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'printing/image.cc')
0 files changed, 0 insertions, 0 deletions