Unstrangle unhandled key event callback for webview

content/browser/renderer_host/ime_adapter_android.cc

Index: content/browser/renderer_host/ime_adapter_android.cc
diff --git a/content/browser/renderer_host/ime_adapter_android.cc b/content/browser/renderer_host/ime_adapter_android.cc
index dbad05cf8b619b442eb549a56f6a87af8dce683e..f1ee0a46dd1bff2adcd8dd796a7afdaf33e12f36 100644
--- a/content/browser/renderer_host/ime_adapter_android.cc
+++ b/content/browser/renderer_host/ime_adapter_android.cc
@@ -151,7 +151,7 @@ bool ImeAdapterAndroid::SendKeyEvent(JNIEnv* env, jobject,
   // If we are going to follow up with a synthetic Char event, then that's the
   // one we expect to test if it's handled or unhandled, so skip handling the
   // "real" event in the browser.
-  event.skip_in_browser = key_down_text_insertion;
+  event.skip_in_browser = true;

[aelias_OOO_until_Jul13, 2015/10/02 20:11:51]

"true" seems unnecessarily broad.  That will suppress browser handling of all
key events (for example, F1-F10 keys), but the intent of benm's patch was just
to suppress the events which are duplicative with a Char event.  I think we
should only broaden suppression to Up events that also correspond to a Char
event.  So I suggest writing: "event.skip_in_browser = event.text[0];" instead.

   rwhva_->SendKeyEvent(event);
   if (key_down_text_insertion) {
     // Send a Char event, but without an os_event since we don't want to