Add functions to generate input events to PPB_Testing_Dev. These make

ppapi/api/dev/ppb_testing_dev.idl

 /* Copyright (c) 2011 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.
  */
 
 /**
  * This file contains interface functions used for unit testing. Do not use in
  * production code. They are not guaranteed to be available in normal plugin
  * environments so you should not depend on them.
  */
 
 label Chrome {
-  M14 = 0.7
+  M14 = 0.7,
+  M15 = 0.8
 };
 
 interface PPB_Testing_Dev {
   /**
    * Reads the bitmap data out of the backing store for the given
    * DeviceContext2D and into the given image. If the data was successfully
    * read, it will return PP_TRUE.
    *
    * This function should not generally be necessary for normal plugin
    * operation. If you want to update portions of a device, the expectation is
@@ skipping 46 matching lines @@
    * associated with this plugin instance. Used for detecting leaks. Returns
    * (uint32_t)-1 on failure.
    */
   uint32_t GetLiveObjectsForInstance([in] PP_Instance instance);
 
   /**
    * Returns PP_TRUE if the plugin is running out-of-process, PP_FALSE
    * otherwise.
    */
   PP_Bool IsOutOfProcess();
+
+  /**
+   * Passes the input event to the renderer, which sends it back to the

[piman, 2011/11/19 22:31:00]

nit: s/renderer/browser/ (here and below)
While it's true that in chrome the renderer process takes care of all this, it's
an implementation detail. From the plugin's point of view, there's only "the
plugin side" and "the browser side", browser being taken in the broad sense -
that's why the interfaces are named PPP and PPB respectively.

[bbudge, 2011/11/20 02:53:57]

Done.

+   * plugin. The plugin should implement PPP_InputEvent and register for
+   * the input event type.
+   *
+   * This method sends an input event through the renderer just as if it had
+   * come from the user. If the renderer determines that it is an event for the
+   * plugin, it will be sent to be handled by the plugin's PPP_InputEvent
+   * interface. When generating mouse events, make sure the position is within
+   * the plugin's area on the page. When generating a keyboard event, make sure
+   * the plugin is focused.
+   *
+   * Note that the renderer may generate extra input events in order to
+   * maintain certain invariants, such as always having a "mouse enter" event
+   * before any other mouse event. Furthermore, the event the plugin receives
+   * after sending a simulated event will be slightly different from the
+   * original event. The renderer will change the timestamp, add modifiers,
+   * and may slightly alter the mouse position, due to coordinate transforms
+   * it performs.
+   */
+  [version=0.8]
+  void SimulateInputEvent([in] PP_Instance instance,
+                          [in] PP_Resource input_event);
 };