From 047f6227bb49d5e315c2da557255035eb22c846f Mon Sep 17 00:00:00 2001 From: "jcampan@chromium.org" Date: Wed, 29 Jul 2009 23:34:56 +0000 Subject: There is no need for the browser process to have an accelerator handler.This CL cleans this up.BUG=NoneTEST=Accelerator should work in Chrome and in the first run window. Review URL: http://codereview.chromium.org/160301 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22020 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/first_run_win.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'chrome/browser/first_run_win.cc') diff --git a/chrome/browser/first_run_win.cc b/chrome/browser/first_run_win.cc index 18b0a44..a00f456 100644 --- a/chrome/browser/first_run_win.cc +++ b/chrome/browser/first_run_win.cc @@ -365,7 +365,8 @@ bool OpenFirstRunDialog(Profile* profile, // is closed) so that the window can receive messages and we block the // browser window from showing up. We pass the accelerator handler here so // that keyboard accelerators (Enter, Esc, etc) work in the dialog box. - MessageLoopForUI::current()->Run(g_browser_process->accelerator_handler()); + views::AcceleratorHandler accelerator_handler; + MessageLoopForUI::current()->Run(&accelerator_handler); process_singleton->Unlock(); return first_run_view->accepted(); -- cgit v1.1