diff options
| author | stuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-26 20:17:50 +0000 |
|---|---|---|
| committer | stuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-26 20:17:50 +0000 |
| commit | 32d0ef5d82ef2e972635245107825e776072dc82 (patch) | |
| tree | 3424f929290716ae4899fea7c961f985579547c2 /chrome/browser/gtk/browser_toolbar_gtk.cc | |
| parent | 61c03cb2e0c5ddaddf8351862e500610c22fdb70 (diff) | |
| download | chromium_src-32d0ef5d82ef2e972635245107825e776072dc82.zip chromium_src-32d0ef5d82ef2e972635245107825e776072dc82.tar.gz chromium_src-32d0ef5d82ef2e972635245107825e776072dc82.tar.bz2 | |
First phase of Mac Keychain integration. For the overall plan, see the design doc linked from the bug. This implements the ability to read existing Keychain passwords, but no storage/updating yet, and no adding of our own metadata as passwords are used; all that will be done in follow-up patches.
This also includes a Keychain wrapper for the functionality necessary so far, and a mock Keychain sufficient to unit-test essentially all of the code.
This patch deliberately excludes the step of instantiating a PasswordStoreMac and hooking it up to the profile, because a bug in autocomplete itself prevents passwords we load from actually being used, and we don't want to trigger Keychain UI for passwords that will be ignored. So this won't be used in builds yet, but it will be unit tested.
BUG=11745
TEST=none (no user-visible effect yet)
Review URL: http://codereview.chromium.org/115658
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16897 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/gtk/browser_toolbar_gtk.cc')
0 files changed, 0 insertions, 0 deletions