Add chrome.input.ime.activate and chrome.input.ime.deactivate API

chrome/common/extensions/api/input_ime.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 [
   {
     "namespace": "input.ime",
     "description": "Use the <code>chrome.input.ime</code> API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window.",
     "types": [
       {
@@ skipping 524 matching lines @@
       },
       {
         "name": "keyEventHandled",
         "type": "function",
         "description": "Indicates that the key event received by onKeyEvent is handled.  This should only be called if the onKeyEvent listener is asynchronous.",
         "platforms": ["chromeos", "win", "linux"],
         "parameters": [
           {"type": "string", "name": "requestId", "description": "Request id of the event that was handled.  This should come from keyEvent.requestId"},
           {"type": "boolean", "name": "response", "description": "True if the keystroke was handled, false if not"}
         ]
+      },
+      {
+        "name": "activate",

[Devlin, 2016/01/13 18:22:59]

Could we instead just have one function, setActive?

[Azure Wei, 2016/01/14 14:03:48]

'setActive' is little wired since we don't have 'getActive' function. Instead,
we have 'onActivate' and 'onDeactivate' events. I think 'activate' and
'deactivate' seem more symmetric and consistent with the two events. Do we have
to change this?

[Devlin, 2016/01/15 22:06:02]

I don't really think setActive is weird, and we try to keep these APIs concise
when we can.  I have a slight preference for setActive over activate/deactivate,
but I don't feel strongly, so either way is fine.

+        "type": "function",
+        "description": "Activates the IME extension itself, so that it can receive events.",
+        "platforms": ["win", "linux"],
+        "parameters": [
+          {
+            "type": "function",
+            "name": "callback",
+            "optional": true,
+            "description": "Called when the operation completes.",
+            "parameters": []
+          }
+        ]
+      },
+      {
+        "name": "deactivate",
+        "type": "function",
+        "description": "Deactivates the IME extension itself, so that it cannot receive events.",
+        "platforms": ["win", "linux"],
+        "parameters": [
+          {
+            "type": "function",
+            "name": "callback",
+            "optional": true,
+            "description": "Called when the operation completes.",
+            "parameters": []
+          }
+        ]
       }
     ],
     "events": [
       {
         "name": "onActivate",
         "type": "function",
         "description": "This event is sent when an IME is activated. It signals that the IME will be receiving onKeyPress events.",
         "platforms": ["chromeos"],
         "parameters": [
           {
@@ skipping 186 matching lines @@
           {
             "type": "string",
             "name": "engineID",
             "description": "ID of the engine receiving the event"
           }
         ]
       }
     ]
   }
 ]