Index: content/common/view_messages.h |
diff --git a/content/common/view_messages.h b/content/common/view_messages.h |
index 1a7508b10c6f559d2eec77af65b9447dc7ede0de..3273387f5db3d7713eae3303a19722b47e6df71a 100644 |
--- a/content/common/view_messages.h |
+++ b/content/common/view_messages.h |
@@ -1695,6 +1695,15 @@ IPC_SYNC_MESSAGE_CONTROL4_2(ViewHostMsg_OpenChannelToPlugin, |
IPC::ChannelHandle /* channel_handle */, |
webkit::WebPluginInfo /* info */) |
+// Sent by the renderer to the browser to start a vibration with the given |
palmer
2013/06/21 18:17:40
Should these be guarded by #if defined(OS_ANDROID)
Michael van Ouwerkerk
2013/06/24 13:46:57
This feature is not necessarily restricted to Andr
|
+// duration. |
+IPC_MESSAGE_CONTROL1(ViewHostMsg_Vibrate, |
+ unsigned int /* milliseconds */) |
palmer
2013/06/21 18:17:40
I'd say int64_t here.
For best results, use an ex
Michael van Ouwerkerk
2013/06/24 13:46:57
Ok, so I changed it to int32_t. I think the use of
|
+ |
+// Sent by the renderer to the browser to cancel the currently running |
+// vibration, if there is one. |
+IPC_MESSAGE_CONTROL0(ViewHostMsg_CancelVibration) |
+ |
#if defined(OS_WIN) |
IPC_MESSAGE_ROUTED1(ViewHostMsg_WindowlessPluginDummyWindowCreated, |
gfx::NativeViewId /* dummy_activation_window */) |