Add DomKey&DomCode to fabricated keydown event if exists

ui/base/ime/input_method_chromeos.cc

Index: ui/base/ime/input_method_chromeos.cc
diff --git a/ui/base/ime/input_method_chromeos.cc b/ui/base/ime/input_method_chromeos.cc
index d49c734a6c6c035f6a9fe9ee2f2da358a6b45c45..924c9cf968321b28c022dbe6553290bc3929d75f 100644
--- a/ui/base/ime/input_method_chromeos.cc
+++ b/ui/base/ime/input_method_chromeos.cc
@@ -361,7 +361,10 @@ void InputMethodChromeOS::ProcessFilteredKeyPressEvent(ui::KeyEvent* event) {
   }
   ui::KeyEvent fabricated_event(ET_KEY_PRESSED,
                                 VKEY_PROCESSKEY,
-                                event->flags());
+                                event->code(),
+                                event->flags(),
+                                event->GetDomKey(),
+                                event->time_stamp());

[Shu Chen, 2016/03/11 16:24:53]

Can you please confirm whether the CJK input methods are impacted by this?

e.g. activate Chinese Pinyin input method, and type 'a' in an input field, the
JS 'keydown' event should have keyCode==229.

[chongz, 2016/03/11 21:17:26]

Sure, but can I have some help on how to include IME in my Chromium build? I'm
following the "simple chrome" guide
(http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chro...)
but it seems that there is no IME installed.

And in addition, may I know why would this CL affect IME? I'm only passing two
new attributes |DomCode| and |DomKey| but didn't change |keyCode|, and this
event will be sent to blink directly.

Please note that this CL is not related to http://crbug.com/593443.

[Shu Chen, 2016/03/14 01:32:17]

Ack. It makes sense.

   ignore_result(DispatchKeyEventPostIME(&fabricated_event));
   if (fabricated_event.stopped_propagation())
     event->StopPropagation();