Implementation for feature policy - vibrate.

third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp

Index: third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp
diff --git a/third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp b/third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp
index 15f48e5afd5ec2757d81be17321ede497e063f1e..1db0c829f80fd89a4039ca1c868477edd0b31b9b 100644
--- a/third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp
+++ b/third_party/WebKit/Source/bindings/core/v8/ConditionalFeatures.cpp
@@ -76,7 +76,9 @@ bool isFeatureEnabledInFrame(const FeaturePolicy::Feature& feature,
                              const LocalFrame* frame) {
   // If there is no frame, or if feature policy is disabled, use defaults.
   bool enabledByDefault =
-      (feature.defaultPolicy != FeaturePolicy::FeatureDefault::DisableForAll);
+      (feature.defaultPolicy == FeaturePolicy::FeatureDefault::EnableForAll ||
+       (feature.defaultPolicy == FeaturePolicy::FeatureDefault::EnableForSelf &&
+        !frame->isCrossOriginSubframe()));

[ojan, 2017/01/19 01:34:29]

Just to complicate things, it looks like we'll be loosening the vibrate
restrictions to disallow vibrate on subframes until the first user gesture in
that frame. So, I think this code will need to be a bit more complicated. I
think we might need EnabledForCrossOriginFramesAfterGesture or something. We'll
want the same thing for top-level-navigation by subframes. 

Whether we want to expose that to web devs via FeaturePolicy is a different
question. I would say no to start with. We can later consider it if we see
developer demand for it.

   if (!RuntimeEnabledFeatures::featurePolicyEnabled() || !frame)
     return enabledByDefault;
   FeaturePolicy* featurePolicy = frame->securityContext()->getFeaturePolicy();