Adding support for DOM3 KeyboardEvents Code in KeyboardEvents

Source/devtools/protocol.json

Index: Source/devtools/protocol.json
diff --git a/Source/devtools/protocol.json b/Source/devtools/protocol.json
index 65cfa6af163d27d7e020151d83bc81e7a27f4fe6..b2f362b12cd9f5633eb32b60cd6b497203cfdf16 100644
--- a/Source/devtools/protocol.json
+++ b/Source/devtools/protocol.json
@@ -4298,6 +4298,7 @@
                     { "name": "text", "type": "string", "optional": true, "description": "Text as generated by processing a virtual key code with a keyboard layout. Not needed for for <code>keyUp</code> and <code>rawKeyDown</code> events (default: \"\")" },
                     { "name": "unmodifiedText", "type": "string", "optional": true, "description": "Text that would have been generated by the keyboard if no modifiers were pressed (except for shift). Useful for shortcut (accelerator) key handling (default: \"\")." },
                     { "name": "keyIdentifier", "type": "string", "optional": true, "description": "Unique key identifier (e.g., 'U+0041') (default: \"\")." },
+                    { "name": "code", "type": "integer", "optional": true, "description": "Unique dom code for each physical key (e.g., '0x07002c') (default: 0)." },

[Wez, 2015/01/08 01:14:47]

s/dom/DOM

The codes aren't defined by DOM, though - DOM defines the string values.

If you want this to stay an integer then it's really an opaque value used by the
embedder to represent a DOM |code| value.

[Habib Virji, 2015/01/12 15:34:17]

Corrected text. Also as you pointed, do not see need of using int and using
string instead to represent |code| value.

[dgozman, 2015/01/12 15:48:16]

This is a public method documented at
https://developer.chrome.com/devtools/docs/protocol/1.1/input#command-dispatc....

It should be useful for developers to pass the |code| parameter, otherwise we
should not change public protocol methods.

[Habib Virji, 2015/01/12 15:58:19]

It can be set by developer. 

The reason it was updated, since InspectorInputAgent::dispatchKeyEvent in turns
call PlatformKeyboardEvent.

Since PlatformKeyboardEvent has been updated to handle new domCode string
parameter, it needed to match. 

                     { "name": "windowsVirtualKeyCode", "type": "integer", "optional": true, "description": "Windows virtual key code (default: 0)." },
                     { "name": "nativeVirtualKeyCode", "type": "integer", "optional": true, "description": "Native virtual key code (default: 0)." },
                     { "name": "autoRepeat", "type": "boolean", "optional": true, "description": "Whether the event was generated from auto repeat (default: false)." },