Add support for DOM3 KeyboardEvent keycode

content/renderer/render_view_impl.h

Index: content/renderer/render_view_impl.h
diff --git a/content/renderer/render_view_impl.h b/content/renderer/render_view_impl.h
index d472f0dec0c9d70ae2cfd954ab5082a9ba4a6487..c6fb77ad2bf8031493d5dabe27589c8dac4c9856 100644
--- a/content/renderer/render_view_impl.h
+++ b/content/renderer/render_view_impl.h
@@ -361,6 +361,8 @@ class CONTENT_EXPORT RenderViewImpl
   virtual void saveImageFromDataURL(const blink::WebString& data_url);
   virtual void didCancelCompositionOnSelectionChange();
   virtual bool handleCurrentKeyboardEvent();
+  virtual blink::WebString domCodeStringFromEnum(int dom_code);
+  virtual int domEnumFromCodeString(const blink::WebString& codeString);

[piman, 2015/01/28 01:18:04]

Why do these need to be virtual members of WebViewImpl? They don't access state,
they could be static.

[Habib Virji, 2015/01/28 10:02:11]

No they do. 

Both functions are trying to access value defined in
ui/events/keycodes/dom4/keycode_converter_data.h. They are kind of helper
function for the values defined on the chromium side to be passed to the blink
side.

[Wez, 2015/01/29 00:51:02]

These are embedder-provided APIs on the WebViewClient - the key event handling
code in Blink needs the embedder to provide them and WebViewClient ended up
being the cleanest place to do that, IIUC.

   virtual bool runFileChooser(
       const blink::WebFileChooserParams& params,
       blink::WebFileChooserCompletion* chooser_completion);