RenderWidgetHost now stores both the WebKeyboardEvent and the native

chrome/browser/renderer_host/render_view_host.cc

 // Copyright (c) 2006-2008 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/renderer_host/render_view_host.h"
 
 #include <string>
 #include <vector>
 
 #include "base/gfx/native_widget_types.h"
@@ skipping 1187 matching lines @@
 void RenderViewHost::OnForwardToDevToolsClient(const IPC::Message& message) {
   RenderViewHostDelegate::View* view = delegate_->GetViewDelegate();
   if (view)
     view->ForwardMessageToDevToolsClient(message);
 }
 
 void RenderViewHost::OnUserMetricsRecordAction(const std::wstring& action) {
   UserMetrics::RecordComputedAction(action.c_str(), process()->profile());
 }
 
-void RenderViewHost::UnhandledKeyboardEvent(const WebKeyboardEvent& event) {
+void RenderViewHost::UnhandledKeyboardEvent(
+    const NativeWebKeyboardEvent& event) {
   RenderViewHostDelegate::View* view = delegate_->GetViewDelegate();
   if (view) {
     // TODO(brettw) why do we have to filter these types of events here. Can't
     // the renderer just send us the ones we care abount, or maybe the view
     // should be able to decide which ones it wants or not?
     if ((event.type == WebInputEvent::RAW_KEY_DOWN) ||
         (event.type == WebInputEvent::KEY_DOWN) ||
         (event.type == WebInputEvent::CHAR)) {
       view->HandleKeyboardEvent(event);
     }
@@ skipping 111 matching lines @@
 void RenderViewHost::RaisePersonalizationEvent(std::string event_name,
                                                std::string event_arg) {
   Send(new ViewMsg_PersonalizationEvent(routing_id(), event_name, event_arg));
 }
 #endif
 
 void RenderViewHost::ForwardMessageFromExternalHost(
     const std::string& message) {
   Send(new ViewMsg_HandleMessageFromExternalHost(routing_id(), message));
 }