Vibration API: use runtime flag, change from client to platform.

public/webpage/WebRuntimeFeatures.h

Index: public/webpage/WebRuntimeFeatures.h
diff --git a/public/webpage/WebRuntimeFeatures.h b/public/webpage/WebRuntimeFeatures.h
index fb91764226c7035d8c6b2c820756b345f894e18c..86b6c59779b185e2e2ebfe814602cb336e205e70 100644
--- a/public/webpage/WebRuntimeFeatures.h
+++ b/public/webpage/WebRuntimeFeatures.h
@@ -208,6 +208,9 @@ public:
     WEBKIT_EXPORT static void enableInputTypeColor(bool);
     WEBKIT_EXPORT static bool isInputTypeColorEnabled();
 
+    WEBKIT_EXPORT static void enableVibration(bool);
+    WEBKIT_EXPORT static bool isVibrationEnabled();

[abarth-chromium, 2013/06/11 23:55:36]

Is there a reason this need to be controllable separately?  Do we not just want
to control it with the usual test/experimental/stable flags?

[Michael van Ouwerkerk, 2013/06/12 16:44:50]

I use these during development to enable the API for Android in
render_thread_impl.cc (AdjustRuntimeFeatureDefaultsForPlatform).

Maybe these should be removed until we find a better use for them. I'll discuss
it with Peter.

+
 private:
     WebRuntimeFeatures();
 };