Make limitations for input.ime.sendKeyEvents API.

ui/base/ime/input_method_base.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "ui/base/ime/input_method_base.h"
 
 #include "base/bind.h"
 #include "base/logging.h"
 #include "base/message_loop/message_loop.h"
 #include "base/strings/utf_string_conversions.h"
@@ skipping 181 matching lines @@
     else
       GetTextInputClient()->ClearCompositionText();
   }
   SendFakeProcessKeyEvent(false);
 }
 
 void InputMethodBase::DeleteSurroundingText(int32_t offset, uint32_t length) {}
 
 void InputMethodBase::SendKeyEvent(KeyEvent* event) {
   sending_key_event_ = true;
+  key_events_for_test.push_back(new KeyEvent(*event));

[Devlin, 2016/06/22 16:33:12]

This never gets cleared in production, right?  And over the course of thousands
of keystrokes, that's non-trivial.

Also, it looks like this will always leak memory, since these are never cleaned
up.

[Azure Wei, 2016/06/23 02:45:23]

Fixed with adding test flag in InputMethod.

   DispatchKeyEvent(event);
   sending_key_event_ = false;
 }
 
+InputMethod* InputMethodBase::GetInputMethod() {
+  return this;
+}
+
+std::vector<ui::KeyEvent*> InputMethodBase::GetKeyEventsForTest() {
+  return key_events_for_test;
+}
+
 }  // namespace ui