Vibration API: plumbing from Blink to Java.

content/common/view_messages.h

Index: content/common/view_messages.h
diff --git a/content/common/view_messages.h b/content/common/view_messages.h
index fc26803f197076bf9cf8086799b2db51847ff02e..ced59cb45d0a54ed4aaa34fc18ffc699be7c48d2 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
+// duration.
+IPC_MESSAGE_CONTROL1(ViewHostMsg_Vibrate,
+                     int32 /* milliseconds */)

[palmer, 2013/06/24 19:07:08]

I really think you're better off using int64_t (== java's long) consistently
everywhere. It makes the whole thing easier to read and reason about, and the
"waste" is negligible.

Integer types are just plain trouble in C++, and especially across languages.
Consistent is simple is good.

[Michael van Ouwerkerk, 2013/06/25 10:56:07]

The windows bots fail to compile because int64_t is not defined. Is that
expected? I can't find a good header to include for defining it. Inside of
content/ it seems mostly the pepper code that uses int64_t. Any ideas?

+
+// 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 */)