Move views::Accelerator to ui in order to use it from aura code.

chrome/browser/ui/views/unhandled_keyboard_event_handler.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/ui/views/unhandled_keyboard_event_handler.h"
 
 #include "base/logging.h"
 #include "views/focus/focus_manager.h"
 
 UnhandledKeyboardEventHandler::UnhandledKeyboardEventHandler() {
@@ skipping 15 matching lines @@
   // cases, we discard the Char events.
   if (event.type == WebKit::WebInputEvent::Char && ignore_next_char_event_) {
     ignore_next_char_event_ = false;
     return;
   }
   // It's necessary to reset this flag, because a RawKeyDown event may not
   // always generate a Char event.
   ignore_next_char_event_ = false;
 
   if (event.type == WebKit::WebInputEvent::RawKeyDown) {
-    views::Accelerator accelerator(
+    ui::Accelerator accelerator(
         static_cast<ui::KeyboardCode>(event.windowsKeyCode),
         (event.modifiers & NativeWebKeyboardEvent::ShiftKey) ==
             NativeWebKeyboardEvent::ShiftKey,
         (event.modifiers & NativeWebKeyboardEvent::ControlKey) ==
             NativeWebKeyboardEvent::ControlKey,
         (event.modifiers & NativeWebKeyboardEvent::AltKey) ==
             NativeWebKeyboardEvent::AltKey);
 
     // This is tricky: we want to set ignore_next_char_event_ if
     // ProcessAccelerator returns true. But ProcessAccelerator might delete
@@ skipping 10 matching lines @@
     ignore_next_char_event_ = false;
   }
 
 #if defined(OS_WIN) && !defined(USE_AURA)
   // Any unhandled keyboard/character messages should be defproced.
   // This allows stuff like F10, etc to work correctly.
   DefWindowProc(event.os_event.hwnd, event.os_event.message,
                 event.os_event.wParam, event.os_event.lParam);
 #endif
 }
-