summaryrefslogtreecommitdiffstats
path: root/chrome/browser/cookie_modal_dialog_views.cc
diff options
context:
space:
mode:
authorjorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-12 21:38:56 +0000
committerjorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-12 21:38:56 +0000
commit8f53962c5743fe97d0c0dd547b5e056a7a68c196 (patch)
treec680ea6d31cb9c518ac9e911e699569abb18b9f4 /chrome/browser/cookie_modal_dialog_views.cc
parent0586b0e71d0b79511d8acbab2e7dedd41c830867 (diff)
downloadchromium_src-8f53962c5743fe97d0c0dd547b5e056a7a68c196.zip
chromium_src-8f53962c5743fe97d0c0dd547b5e056a7a68c196.tar.gz
chromium_src-8f53962c5743fe97d0c0dd547b5e056a7a68c196.tar.bz2
Make the setItem CONTENT_SETTING_ASK dialog more useful by showing the actual key and value. Unfortunately, we're going to have to abuse cookie strings for 4.1 Once this goes in, I'll add new strings for the actual fields.
This also cleans up the code some. TEST=Instead of size/modified information you'll see "name" and "content" in the dialog that comes up when asking whether to allow local storage. BUG=none Review URL: http://codereview.chromium.org/597061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38952 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/cookie_modal_dialog_views.cc')
-rw-r--r--chrome/browser/cookie_modal_dialog_views.cc5
1 files changed, 1 insertions, 4 deletions
diff --git a/chrome/browser/cookie_modal_dialog_views.cc b/chrome/browser/cookie_modal_dialog_views.cc
index 6e9027a..c8930c1 100644
--- a/chrome/browser/cookie_modal_dialog_views.cc
+++ b/chrome/browser/cookie_modal_dialog_views.cc
@@ -41,10 +41,7 @@ NativeDialog CookiePromptModalDialog::CreateNativeDialog() {
#if defined(OS_WIN)
return new CookiePromptView(this,
tab_contents_->GetMessageBoxRootWindow(),
- tab_contents_->profile(),
- storage_info_,
- host_, cookie_line_, delegate_,
- cookie_ui_);
+ tab_contents_->profile());
#else
return NULL;
#endif