Remove ui::KeycodeConverter::CodeToNativeKeycode().

content/renderer/pepper/usb_key_code_conversion_win.cc

-// Copyright (c) 2012 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 "content/renderer/pepper/usb_key_code_conversion.h"
-
-#include "base/basictypes.h"
-#include "third_party/WebKit/public/web/WebInputEvent.h"
-#include "ui/events/keycodes/dom4/keycode_converter.h"
-
-using blink::WebKeyboardEvent;
-
-namespace content {
-
-uint32_t UsbKeyCodeForKeyboardEvent(const WebKeyboardEvent& key_event) {
-  // Extract the scancode and extended bit from the native key event's lParam.
-  int scancode = (key_event.nativeKeyCode >> 16) & 0x000000FF;
-  if ((key_event.nativeKeyCode & (1 << 24)) != 0)
-    scancode |= 0xe000;

[Wez, 2015/05/06 23:37:28]

nit: Initially I thought we were missing this logic in the new code, which has
it in GetScaneCodeFromLParam in event_win.cc; the comment on that function, and
on the related CodeForWindowsScanCode should ideally be updated to make clear
the form that our version of "windows scancodes" take (i.e. that we fold the
extended bit and OEM scancode together to get a PS/2-like scancode).

-
-  return ui::KeycodeConverter::NativeKeycodeToUsbKeycode(scancode);
-}
-
-const char* CodeForKeyboardEvent(const WebKeyboardEvent& key_event) {
-  // Extract the scancode and extended bit from the native key event's lParam.
-  int scancode = (key_event.nativeKeyCode >> 16) & 0x000000FF;
-  if ((key_event.nativeKeyCode & (1 << 24)) != 0)
-    scancode |= 0xe000;
-
-  return ui::KeycodeConverter::NativeKeycodeToCode(scancode);
-}
-
-}  // namespace content