Index: ppapi/api/dev/ppb_testing_dev.idl |
=================================================================== |
--- ppapi/api/dev/ppb_testing_dev.idl (revision 110829) |
+++ ppapi/api/dev/ppb_testing_dev.idl (working copy) |
@@ -10,7 +10,8 @@ |
*/ |
label Chrome { |
- M14 = 0.7 |
+ M14 = 0.7, |
+ M15 = 0.8 |
}; |
interface PPB_Testing_Dev { |
@@ -77,4 +78,28 @@ |
* 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
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); |
}; |