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

public/webpage/WebRuntimeFeatures.h

 /*
  * Copyright (C) 2013 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 190 matching lines @@
 
     WEBKIT_EXPORT static void enableWebPInAcceptHeader(bool);
     WEBKIT_EXPORT static bool isWebPInAcceptHeaderEnabled();
 
     WEBKIT_EXPORT static void enableDataListElement(bool);
     WEBKIT_EXPORT static bool isDataListElementEnabled();
 
     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();
 };
 
 } // namespace WebKit
 
 #endif