linux-aura: Supports Compose key with XIM.

ui/events/event.h

Index: ui/events/event.h
diff --git a/ui/events/event.h b/ui/events/event.h
index 17cad8b301ecd1c37f2cc04c5de8845b97743507..144612d145901132b048f5e1bc916cb4b9937a8b 100644
--- a/ui/events/event.h
+++ b/ui/events/event.h
@@ -550,6 +550,8 @@ class EVENTS_EXPORT KeyEvent : public Event {
   KeyboardCode key_code() const { return key_code_; }
   bool is_char() const { return is_char_; }
 
+  bool is_fabricated_by_ime() const { return is_fabricated_by_ime_; }
+
   // This is only intended to be used externally by classes that are modifying
   // events in EventFilter::PreHandleKeyEvent().  set_character() should also be
   // called.
@@ -584,6 +586,10 @@ class EVENTS_EXPORT KeyEvent : public Event {
   // share the same type: ET_KEY_PRESSED.
   bool is_char_;
 
+  // True if the key event is fabricated by the underlying IME and not resulting
+  // from an user action.
+  bool is_fabricated_by_ime_;

[sadrul, 2014/04/18 19:01:48]

How is this different from TranslatedKeyEvent? What's the plan for addressing
crbug.com/339355?

[Yuki, 2014/04/21 02:38:30]

TranslatedKeyEvent represents that:
1. The key event was generated by a real user action as same as KeyEvent, and
2. Our own IMF/IME has already processed the event once, so there is no need to
pass the event to IMF/IME again.  (So we can avoid infinite loop.)

is_fabricated_by_ime_ represents that:
1. The key event was NOT DIRECTLY generated by a user action.  Some IMEs need
hacky tricks that add fake key events to the event queue.  This is that kind of
fake key event.
2. Thus, we need to pass this key event to the underlying IME.

So they're totally different things.  I remember crbug.com/339355 and will
address separately.

[sadrul, 2014/04/22 15:34:29]

I think it will be cleaner to have this as a KeyEventFlag instead.

[Yuki, 2014/04/23 08:08:24]

Done.

+
   uint16 character_;
 };