mash: Don't synthesize extra key press events in the window server

chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc

Index: chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc
diff --git a/chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc b/chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc
index a74e7bf441dec7032ffd5558c3488bb9a667415e..991f1e636d1b2703db82d51d125a3a91ec073ff6 100644
--- a/chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc
+++ b/chrome/browser/ui/views/ime_driver/input_method_bridge_chromeos.cc
@@ -37,10 +37,7 @@ void InputMethodBridge::ProcessKeyEvent(
     input_method_chromeos_->DispatchKeyEvent(
         key_event, base::MakeUnique<base::Callback<void(bool)>>(callback));
   } else {
-    // On Linux (include ChromeOS), the mus emulates the WM_CHAR generation
-    // behaviour of Windows. But for ChromeOS, we don't expect those char
-    // events, so we filter them out.
-    const bool handled = true;
+    const bool handled = false;
     callback.Run(handled);
   }
 }