Do not register IME app window in launcher

extensions/browser/app_window/app_window.h

Index: extensions/browser/app_window/app_window.h
diff --git a/extensions/browser/app_window/app_window.h b/extensions/browser/app_window/app_window.h
index 8d6ffea1c08b24193b260e1407a89693d3f0ac21..e91a0ad197f1ab1d80d6633b29f1e6c990a40820 100644
--- a/extensions/browser/app_window/app_window.h
+++ b/extensions/browser/app_window/app_window.h
@@ -351,6 +351,9 @@ class AppWindow : public content::NotificationObserver,
   // Whether the app window wants to be alpha enabled.
   bool requested_alpha_enabled() const { return requested_alpha_enabled_; }
 
+  // Whether the app window is created by IME extensions.

[Mr4D (OOO till 08-26), 2015/03/02 16:44:12]

Hmm. Since there is only a single use case for this yet - maybe we should name
this "hide_app_window_in_launcher()" (and also name the var accordingly)?

If you have the feeling that the "ime" information is more valuable however you
can leave that.

[bshe, 2015/03/02 17:40:36]

Right. It is only used for one case now. But I am in the process of developing
new keyboard and we might need it to do more customization for IME windows, i.e.
always on top, movable. So I am in favor of keeping the ime name for now. If
later I found no other use case, I will change it to
hide_app_window_in_launcher. Added a todo.

+  bool is_ime_window() const { return is_ime_window_; }
+
   void SetAppWindowContentsForTesting(scoped_ptr<AppWindowContents> contents) {
     app_window_contents_ = contents.Pass();
   }
@@ -555,6 +558,9 @@ class AppWindow : public content::NotificationObserver,
   // Whether |alpha_enabled| was set in the CreateParams.
   bool requested_alpha_enabled_;
 
+  // Whether |is_ime_window| was set in the CreateParams.
+  bool is_ime_window_;
+
   base::WeakPtrFactory<AppWindow> image_loader_ptr_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(AppWindow);