[NOT FOR COMMIT] Ignore inserting characters of Keys with modifiers on CrOS

content/browser/renderer_host/render_widget_host_view_aura.cc

Index: content/browser/renderer_host/render_widget_host_view_aura.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_aura.cc b/content/browser/renderer_host/render_widget_host_view_aura.cc
index f8fdba0e1ab225ce0944c70822ccb2c63ade0c6c..262b92d6eae96132fdde34ca007e0e576678e587 100644
--- a/content/browser/renderer_host/render_widget_host_view_aura.cc
+++ b/content/browser/renderer_host/render_widget_host_view_aura.cc
@@ -1585,8 +1585,19 @@ void RenderWidgetHostViewAura::InsertChar(base::char16 ch, int flags) {
   if (host_ && (accept_return_character_ || ch != ui::VKEY_RETURN)) {
     double now = ui::EventTimeForNow().InSecondsF();
     // Send a blink::WebInputEvent::Char event to |host_|.
+    // On ChromeOS we send a blink::WebInputEvent::Char event only if no
+    // modifiers are currently pressed. Otherwise |is_char| will be false and we
+    // will end up sending a blink::WebInputEvent::RawKeyDown event.
+#if defined(OS_CHROMEOS)

[afakhry, 2015/08/14 20:18:55]

I'm not sure if we want to ignore keys with modifiers on other platforms too?
For now I'm just doing it for CrOs.

+    const int kControlModifierMask = ui::EF_CONTROL_DOWN | ui::EF_ALT_DOWN |
+                                     ui::EF_COMMAND_DOWN;
+#else
+    const int kControlModifierMask = ui::EF_NONE;
+#endif  // defined(OS_CHROMEOS)
+    const bool is_char = (flags & kControlModifierMask) == 0;
+
     NativeWebKeyboardEvent webkit_event(ui::ET_KEY_PRESSED,
-                                        true /* is_char */,
+                                        is_char,

[dtapuska, 2015/09/03 15:27:12]

This doesn't seem correct to me.

This is going to generate two keydown events in javascript and not a keydown,
keypress, keyup sequence as intended.

You should try this page http://nonan.jp/keyevent/input.html

and see the sequence of events for each. I suspect you'll start seeing a
duplicated keydown event which is incorrect.

[afakhry, 2015/09/03 17:34:03]

You are right, I used to get two keydowns. I changed it to avoid sending the
event altogether if |is_char| is false. I validated that behavior of pressing
Ctrl+Q matches that of Search+Q using the test page you provided.

                                         ch,
                                         flags,
                                         now);