Chromium Code Reviews| Index: ppapi/api/private/ppb_input_event_private.idl |
| diff --git a/ppapi/api/private/ppb_input_event_private.idl b/ppapi/api/private/ppb_input_event_private.idl |
| new file mode 100644 |
| index 0000000000000000000000000000000000000000..b655e1dc5e63905b984abf69e8d0196a9faefab1 |
| --- /dev/null |
| +++ b/ppapi/api/private/ppb_input_event_private.idl |
| @@ -0,0 +1,39 @@ |
| +/* Copyright (c) 2014 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 defines the PPB_InputEvent_Private interfaces. |
| + */ |
| + |
| +label Chrome { |
| + M36 = 0.1 |
| +}; |
| + |
| +/** |
| + * The <code>PPB_InputEvent_Private</code> interface contains pointers to several |
| + * functions related to generic input events on the browser. |
| + */ |
| + |
| +interface PPB_InputEvent_Private { |
| + /** |
| + * TraceInputLatency() traces the latency of the input event. The input |
| + * latency is shown in the trace viewer. The starting point of the input |
| + * latency is when the input event is sent from renderer to plugin. If the |
| + * input event does not cause any rendering damage, the end point of input |
| + * latency is when TraceInputLatency() is called on the event. If the input |
| + * event does cause rendering damage, the end point of input latency is when |
| + * the resulted plugin frame eventually reaches screen. |
|
dmichael (off chromium)
2014/05/05 22:20:32
There are some caveats with this in your current p
Yufeng Shen (Slow to review)
2014/05/07 17:12:14
Extra notes added.
|
| + * |
| + * @param[in] event A <code>PP_Resource</code> corresponding to an input |
| + * event. |
| + * |
| + * @param[in] has_damage A bool indicating whether the event has caused any |
| + * rendering damage. |
| + */ |
| + |
| + void TraceInputLatency([in] PP_Resource event, |
| + [in] PP_Bool has_damage); |
| +}; |
| + |