Allow component IME extension use app.window and add 'ime' window type for app window

chrome/common/extensions/api/app_window.idl

Index: chrome/common/extensions/api/app_window.idl
diff --git a/chrome/common/extensions/api/app_window.idl b/chrome/common/extensions/api/app_window.idl
index caff663e29def5edda094f0f520ba3571bbe3072..d23926520d088df96af05058e0cf2644fe35422b 100644
--- a/chrome/common/extensions/api/app_window.idl
+++ b/chrome/common/extensions/api/app_window.idl
@@ -215,6 +215,12 @@ namespace app.window {
     // Type of window to create.
     [nodoc] WindowType? type;
 
+    // Creates a special ime window. This window is not focusable and can be
+    // stacked above virtual keyboard window. This is restriced to component ime
+    // extensions.
+    // Requires app.window.ime API permission.
+    [nodoc] boolean? ime;
+
     // Frame type: <code>none</code> or <code>chrome</code> (defaults to
     // <code>chrome</code>). For <code>none</code>, the
     // <code>-webkit-app-region</code> CSS property can be used to apply
@@ -369,6 +375,9 @@ namespace app.window {
     // TODO(jackhou): Document this properly before going to stable.
     [nodoc] static boolean alphaEnabled();
 
+    // Is the window an ime window?
+    [nodoc] static boolean isImeWindow();

[jackhou1, 2014/09/12 03:24:51]

Is this necessary? For alphaEnabled, requesting alphaEnabled:true does not
guarantee an alpha enabled window, so the window is expected to check what it
got. For IME, I think we either guarantee an IME window, or fail to create the
window, so the extension wouldn't need to check this.

[bshe, 2014/09/12 17:44:12]

I thought that IME extensions can create non-ime window. But since you and ben
both dont like the idea, I have changed the code so that IME extensions can only
create IME window. In that case, this is not necessary. Removed.

On 2014/09/12 03:24:51, jackhou1 wrote:

+
     // The JavaScript 'window' object for the created child.
     [instanceOf=Window] object contentWindow;