Integrate the new input method API for Views into Chromium.

views/focus/focus_manager.cc

Index: views/focus/focus_manager.cc
diff --git a/views/focus/focus_manager.cc b/views/focus/focus_manager.cc
index 5712b2e993a44a302f077719859b84b1eb28fdd7..93731e7b5561f94f75f612ba303a115cfa6871a2 100644
--- a/views/focus/focus_manager.cc
+++ b/views/focus/focus_manager.cc
@@ -368,10 +368,6 @@ void FocusManager::RestoreFocusedView() {
           focus_change_reason_ = kReasonFocusRestore;
       }
     }
-  } else {
-    // Clearing the focus will focus the root window, so we still get key
-    // events.
-    ClearFocus();

[Jay Civelli, 2011/03/28 16:04:36]

Why don't we need this anymore?

[James Su, 2011/03/28 16:54:12]

I can't see any reason to call ClearFocus() here, because: 1.
RestoreFocusedView() is called when the top-level window is activated (focused),
calling ClearFocus() to focus the root window again is not necessary at all.
2. A View may be focused even before the top-level window gets activated,
calling ClearFocus() here will clear the focused view unexpectedly.

Actually I guess got_initial_focus_in_ in WidgetGtk was introduced as a
workaround of this issue.

   }
 }