Adding support for DOM3 KeyboardEvents Code in KeyboardEvents

Source/core/inspector/InspectorInputAgent.h

Index: Source/core/inspector/InspectorInputAgent.h
diff --git a/Source/core/inspector/InspectorInputAgent.h b/Source/core/inspector/InspectorInputAgent.h
index 7775a7427451546d441d6cbd35b685c4826b9717..11f639331b249074c3ecc7e3a1e8107716824dc8 100644
--- a/Source/core/inspector/InspectorInputAgent.h
+++ b/Source/core/inspector/InspectorInputAgent.h
@@ -54,7 +54,7 @@ public:
     virtual void trace(Visitor*) override;
 
     // Methods called from the frontend for simulating input.
-    virtual void dispatchKeyEvent(ErrorString*, const String& type, const int* modifiers, const double* timestamp, const String* text, const String* unmodifiedText, const String* keyIdentifier, const int* windowsVirtualKeyCode, const int* nativeVirtualKeyCode, const bool* autoRepeat, const bool* isKeypad, const bool* isSystemKey) override;
+    virtual void dispatchKeyEvent(ErrorString*, const String& type, const int* modifiers, const double* timestamp, const String* text, const String* unmodifiedText, const String* keyIdentifier, const int* domCode, const int* windowsVirtualKeyCode, const int* nativeVirtualKeyCode, const bool* autoRepeat, const bool* isKeypad, const bool* isSystemKey) override;

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

Why is domCode an int* rather than a String*?

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

Since this is the value that was the input, while string value is obtained via
chromium. Since these values are input, was using int for representing the
opaque values. 

     virtual void dispatchMouseEvent(ErrorString*, const String& type, int x, int y, const int* modifiers, const double* timestamp, const String* button, const int* clickCount) override;
     virtual void dispatchTouchEvent(ErrorString*, const String& type, const RefPtr<JSONArray>& touchPoints, const int* modifiers, const double* timestamp) override;
 private: