New method: InputMethod::IsCandidatePopupOpen()

ui/base/ime/input_method.h

Index: ui/base/ime/input_method.h
diff --git a/ui/base/ime/input_method.h b/ui/base/ime/input_method.h
old mode 100644
new mode 100755
index 61b628c6db0e6e86abbdb5a6c57fe23e4f4feaa8..cccf9336cd90d7a0fa00b5354c0e7a818e5bfe5c
--- a/ui/base/ime/input_method.h
+++ b/ui/base/ime/input_method.h
@@ -147,6 +147,11 @@ class InputMethod {
   // Checks if the focused text input client supports inline composition.
   virtual bool CanComposeInline() const = 0;
 
+  // Returns true if a candidate window (or IME suggest, etc.) is open.
+  // Returns false if no popup window is open or the detection of IME popups
+  // is not supported.
+  virtual bool IsPopupOpen() const = 0;

[Seigo Nonaka, 2013/06/19 09:15:51]

IsPopupOpen seems not clear for me.
How about IsCandidateWindowOpen or IsInputMethodUIActive?

By the way, is it okay to get only open or not?
I guess you are trying to integrate omnibox suggestion and candidate window.
introducing observer is more helpful?

[Yuki, 2013/06/19 09:35:54]

For name, I'd like to support in near future not only candidate windows, but
also IME suggest or anything similar.  So I thought "CandidateWindow" is too
specific.  From the view point of UI component, I think it's best to say
"Popup".  I'd like to cover any sort of popups, which would conflict with
Omnibox popup.

For observer, it's not helpful this time.  At
OmniboxPopupContentsView::UpdatePopupAppearance(), I'd like to check if any IME
popups are open or not.  So a simple getter method is more useful than a
observer.

+
   // Management of the observer list.
   virtual void AddObserver(InputMethodObserver* observer) = 0;
   virtual void RemoveObserver(InputMethodObserver* observer) = 0;