Add functions to generate input events to PPB_Testing_Dev. These make

ppapi/c/dev/ppb_testing_dev.h

Index: ppapi/c/dev/ppb_testing_dev.h
===================================================================
--- ppapi/c/dev/ppb_testing_dev.h	(revision 108154)
+++ ppapi/c/dev/ppb_testing_dev.h	(working copy)
@@ -12,8 +12,6 @@
 
 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

[dmichael (off chromium), 2011/11/07 17:12:58]

I think in general we still need to rev the interface. Imagine that a
plugin/nexe which wants to use the new function is run against an older version
of Chrome that doesn't have the function. Bad things will ensue, and the
plugin/nexe won't really have any recourse.

It *probably* doesn't matter since this is only used internally. But I think the
safest course is to rev the interface.

[bbudge, 2011/11/08 00:05:05]

Done.

 
@@ -74,6 +72,17 @@
   // 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.
+  //
+  // Note that this method doesn't send the event through the entire renderer
+  // layer, since this can cause the plugin to receive other events that may
+  // be generated there. This is intended to give the plugin the ability to
+  // simulate an exact sequence of events, and to generate a "user gesture"
+  // in order to test functionality that requires one.
+  void (*SimulateInputEvent)(PP_Instance instance, PP_Resource input_event);
 };
 
 #endif  /* PPAPI_C_DEV_PPB_TESTING_DEV_H_ */