Add functions to generate input events to PPB_Testing_Dev. These make

ppapi/c/dev/ppb_testing_dev.h

 /* 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.
  */
 #ifndef PPAPI_C_DEV_PPB_TESTING_DEV_H_
 #define PPAPI_C_DEV_PPB_TESTING_DEV_H_
 
 #include "ppapi/c/pp_bool.h"
 #include "ppapi/c/pp_instance.h"
 #include "ppapi/c/pp_resource.h"
 #include "ppapi/c/pp_stdint.h"
 
 struct PP_Point;
 
-// TODO(dmichael): Delete support for 0.6.
-#define PPB_TESTING_DEV_INTERFACE_0_6 "PPB_Testing(Dev);0.6"
 #define PPB_TESTING_DEV_INTERFACE_0_7 "PPB_Testing(Dev);0.7"
-#define PPB_TESTING_DEV_INTERFACE PPB_TESTING_DEV_INTERFACE_0_7
+#define PPB_TESTING_DEV_INTERFACE_0_8 "PPB_Testing(Dev);0.8"
+#define PPB_TESTING_DEV_INTERFACE PPB_TESTING_DEV_INTERFACE_0_8
 
 // This interface contains 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.
 struct 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
@@ skipping 38 matching lines @@
   void (*QuitMessageLoop)(PP_Instance instance);
 
   // Returns the number of live objects (resources + strings + objects)
   // associated with this plugin instance. Used for detecting leaks. Returns
   // (uint32_t)-1 on failure.
   uint32_t (*GetLiveObjectsForInstance)(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
+  // 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 wheel events, make sure to
+  // precede it with a mouse event inside the plugin's area. When generating a
+  // keyboard event, make sure the plugin has focus.
+  //
+  // 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 slightly change mouse position, due to the complex coordinate
+  // transforms it performs.
+  void (*SimulateInputEvent)(PP_Instance instance, PP_Resource input_event);
+};
+
+struct PPB_Testing_Dev_0_7 {
+  PP_Bool (*ReadImageData)(PP_Resource device_context_2d,
+                           PP_Resource image,
+                           const struct PP_Point* top_left);
+  void (*RunMessageLoop)(PP_Instance instance);
+  void (*QuitMessageLoop)(PP_Instance instance);
+  uint32_t (*GetLiveObjectsForInstance)(PP_Instance instance);
+  PP_Bool (*IsOutOfProcess)();
 };
 
 #endif  /* PPAPI_C_DEV_PPB_TESTING_DEV_H_ */