New accessibility virtual keyboard behavior in non-sticky mode.

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
index 67010a3f65822ed9f33046885653e332e4c8d747..6b1d526e9f1981055ecc27c197806122ece48035 100644
--- a/ui/base/ime/input_method.h
+++ b/ui/base/ime/input_method.h
@@ -15,6 +15,7 @@
 #include "build/build_config.h"
 #include "ui/base/ime/text_input_mode.h"
 #include "ui/base/ime/text_input_type.h"
+#include "ui/gfx/geometry/rect.h"
 
 namespace extensions {
 class InputImeApiTest;
@@ -160,6 +161,9 @@ class InputMethod {
   virtual void AddObserver(InputMethodObserver* observer) = 0;
   virtual void RemoveObserver(InputMethodObserver* observer) = 0;
 
+  // Set screen bounds of a on-screen keyboard.
+  virtual void SetOnScreenKeyboardBounds(const gfx::Rect& new_bounds) {}

[Shu Chen, 2017/03/14 14:42:30]

Looks like this interface method is added only for storing the keyboard_bounds
in InputMethod.
It would be better to avoid adding this and instead let the TextInputClient
store it by itself.

[yhanada, 2017/03/15 12:54:32]

The stored keyboard bounds is used when switching TextInputClient (please see
InputMethodBase::SetFocusedTextInputClient). I chose to store it in InputMethod
because the keyboard bounds depends on what IME is used and the bounds is used
across multiple TextInputClient.

What do you think?

+
  protected:
   friend class extensions::InputImeApiTest;