Consolidate OnKeyEvent and InputMethod code.

views/focus/accelerator_handler_touch.cc

Index: views/focus/accelerator_handler_touch.cc
diff --git a/views/focus/accelerator_handler_touch.cc b/views/focus/accelerator_handler_touch.cc
index 716cb299ac5912426897383d69fba81f4d4c1d94..a18bbe1f98e521de2b62ba00a66e40f76215cad7 100644
--- a/views/focus/accelerator_handler_touch.cc
+++ b/views/focus/accelerator_handler_touch.cc
@@ -179,14 +179,7 @@ bool DispatchXEvent(XEvent* xev) {
       case KeyRelease: {
         Event::FromNativeEvent2 from_native;
         KeyEvent keyev(xev, from_native);
-        InputMethod* ime = widget->GetInputMethod();
-        // Always dispatch key events to the input method first, to make sure
-        // that the input method's hotkeys work all time.
-        if (ime) {
-          ime->DispatchKeyEvent(keyev);
-          return true;
-        }
-        return root->ProcessKeyEvent(keyev);
+        return widget->OnKeyEvent(keyev);

[James Su, 2011/04/25 03:37:03]

This change breaks IME when using hardware keyboard.

[James Su, 2011/04/25 03:46:32]

To be more clear: we always need to dispatch a key event to the input method
before views hierarchy. Otherwise, even though most key events may be dispatched
to the input method through WidgetGtk::OnEventKey if widget->OnKeyEvent(keyev)
returns false, functions of the input method may be broken if some keys are
handled in widget->OnKeyEvent(keyev).
And this change may cause a key event to be dispatched to views hierarchy twice.

[msw, 2011/04/25 17:52:38]

Done. Logic restored with updated call to Widget.

       }
 
       case ButtonPress: