Switch from text insertion to key press and release events on the virtual k…

chrome/common/extensions/api/experimental_input_virtual_keyboard.json

Index: chrome/common/extensions/api/experimental_input_virtual_keyboard.json
diff --git a/chrome/common/extensions/api/experimental_input_virtual_keyboard.json b/chrome/common/extensions/api/experimental_input_virtual_keyboard.json
index 4bd2c81e0e1180aacaf536c6333085605ea35995..0590ac3bf0c1f8fa4b1b714bf4101f689a9e5f8a 100644
--- a/chrome/common/extensions/api/experimental_input_virtual_keyboard.json
+++ b/chrome/common/extensions/api/experimental_input_virtual_keyboard.json
@@ -23,6 +23,27 @@
             "parameters": []
           }
         ]
+      },
+      {
+        "name": "dispatchKeyEvent",
+        "type": "function",
+        "description": "Dispatches a fabricated key event to the focused input field.",
+        "parameters": [
+          { "name": "type",

[bshe, 2013/07/25 15:33:05]

probably add a enum field here like this
(https://code.google.com/p/chromium/codesearch/#chromium/src/chrome/common/ext...
It could give us a js console error when type is not "keyPressed" or
"keyReleased".

But you have error detection in keyboard_util for extension and webui parameter.
So this is not necessary, just thought it might be slightly clearer to have a js
console error.

[kevers, 2013/07/26 00:53:30]

Added enum.

+            "type": "string",
+            "description": "Type type of key event: keyPressed or keyReleased."
+          },
+          { "name": "charCode",
+            "type": "integer",
+            "description": "Unicode value of the character."         
+          },
+          { "name": "callback",
+            "type": "function",
+            "optional": true,
+            "description": "Called post event dispatch.",
+            "parameters": []
+          }
+        ]
       }
     ]
   }