Add AcceleratorType to EventMatcher

components/mus/public/interfaces/input_event_matcher.mojom

Index: components/mus/public/interfaces/input_event_matcher.mojom
diff --git a/components/mus/public/interfaces/input_event_matcher.mojom b/components/mus/public/interfaces/input_event_matcher.mojom
index 3e0929da2dd4fbc4d092afff750fa1be4501eba5..1cc73d8513308425691c1b30f837e78a77114a9e 100644
--- a/components/mus/public/interfaces/input_event_matcher.mojom
+++ b/components/mus/public/interfaces/input_event_matcher.mojom
@@ -8,6 +8,11 @@ import "components/mus/public/interfaces/input_event_constants.mojom";
 import "components/mus/public/interfaces/input_key_codes.mojom";
 import "ui/mojo/geometry/geometry.mojom";
 
+
+struct AcceleratorPhaseMatcher {
+  AcceleratorPhase accelerator_phase;
+};
+
 struct KeyEventMatcher {
   KeyboardCode keyboard_code;
 };
@@ -42,6 +47,7 @@ struct EventFlagsMatcher {
 // A matcher to match any key-press event would be:
 // - |type_matcher.type| = mus::mojom::EventType::KEY_PRESSED
 struct EventMatcher {
+  AcceleratorPhaseMatcher accelerator_matcher;

[sky, 2016/03/04 16:51:55]

As the phase is always required can you do away with the struct and use the enum
directly here?

[jonross, 2016/03/04 20:38:20]

Certainly. Thought that will imply a default.

I would be fine with defaulting to pre-target phase. However we could add an
'undefined' phase as the default, and require apps to specify which one.

Thoughts?

[sky, 2016/03/04 21:36:16]

Ah, I see what you're saying. I'm fine with pretarget.

[jonross, 2016/03/04 22:13:03]

Awesome. Done.

   EventTypeMatcher? type_matcher;
   EventFlagsMatcher? flags_matcher;
   // These flags will be stripped from incoming events' flags when comparing