Add InputScope support into InputMethodIMM32

ui/base/ime/input_method_imm32.cc

Index: ui/base/ime/input_method_imm32.cc
diff --git a/ui/base/ime/input_method_imm32.cc b/ui/base/ime/input_method_imm32.cc
index 41f65dfb37dba4d40698cd3aad4da08ff5f17f6b..400fd207f6d2fd2cd7aa8dfd3fa736bf897f37f8 100644
--- a/ui/base/ime/input_method_imm32.cc
+++ b/ui/base/ime/input_method_imm32.cc
@@ -7,6 +7,7 @@
 #include "base/basictypes.h"
 #include "ui/base/ime/composition_text.h"
 #include "ui/base/ime/text_input_client.h"
+#include "ui/base/ime/win/tsf_input_scope.h"
 
 
 namespace ui {
@@ -278,6 +279,8 @@ void InputMethodIMM32::UpdateIMEState() {
   }
 
   imm32_manager_.SetTextInputMode(window_handle, GetTextInputMode());
+  tsf_inputscope::SetInputScopeForTsfUnawareWindow(
+      window_handle, GetTextInputType(), GetTextInputMode());

[yoichio, 2013/09/23 12:09:54]

Can we cache values of GetTextInputType() and *Mode() in this scope?

[yukawa, 2013/09/23 17:54:21]

I think we can in this particular case, although this is not a trivial question
in general.

We should make a snapshot of state if and only if
  A. the state is guaranteed to be immutable in the scope
or
  B. the state might be changed in the scope but we should use the initial state
intentionally.

In this case, |imm32_manager_.DisableIME|, |imm32_manager_.EnableIME|, and
|imm32_manager_.SetTextInputMode| might have side side effect.

Apparently InputMethodIMM32::UpdateIMEState is not designed to be reentrant.
Paradoxically it means that we assume the case A is implicitly applied in this
function. This is why I think we can *cache* the state in this particular case.

 }
 
 }  // namespace ui