Adding support for DOM3 KeyboardEvents Code in KeyboardEvents

public/web/WebViewClient.h

Index: public/web/WebViewClient.h
diff --git a/public/web/WebViewClient.h b/public/web/WebViewClient.h
index fa39080f10f3357a060fe897c946eee91b29d73e..494ad2af7c40a5908709adfd63388136b5a88d37 100644
--- a/public/web/WebViewClient.h
+++ b/public/web/WebViewClient.h
@@ -134,6 +134,13 @@ public:
     // indicating that the default action should be suppressed.
     virtual bool handleCurrentKeyboardEvent() { return false; }
 
+    // This method converts from the supplied enum value for the key

[Rick Byers, 2015/01/23 20:38:30]

I'm OK using an opaque 'int' here (there are some other examples in the blink
Web API), but only if we're as precise as possible in the comments about where
the meaning of this value is defined.

Also, for both APIs, please define what should happen with unknown/invalid
input.

[Habib Virji, 2015/01/26 11:32:35]

Done.

+    // to the embedder's DOM |code| string.
+    virtual WebString domCodeStringFromEnum(int domCode) { return ""; }

[Rick Byers, 2015/01/23 20:38:30]

Again, let's be precise about the "enum" in question here.  What's the best term
for consistency with chromium - "DOM code value" perhaps?  

Perhaps domCodeStringFromDomCodeValue?

[Wez, 2015/01/23 20:59:49]

IMO "DOM code string" and "DOM code enum" make most sense; "DOM code value"
sounds ambiguous as to whether it means the string or the opaque Chromium enum.

kpschoedel@, does that make sense to you?

[Habib Virji, 2015/01/26 11:32:35]

Done.

+
+    // This method converts from the suppled DOM |code| string to the
+    // embedder's enum value for the key.
+    virtual int domEnumFromCodeString(const WebString& codeString) { return 0; }
 
     // Dialogs -------------------------------------------------------------