Block navigator.vibrate in cross-domain iframe.

third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp

Index: third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp
diff --git a/third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp b/third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp
index 50e5ce29ebf0b5d6baff3a91dfdb0d42f0616a0a..3d0c82fe1209d8ee5ef2618735950dc002ce1cb1 100644
--- a/third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp
+++ b/third_party/WebKit/Source/modules/vibration/NavigatorVibration.cpp
@@ -20,6 +20,7 @@
 #include "modules/vibration/NavigatorVibration.h"
 
 #include "core/dom/Document.h"
+#include "core/frame/LocalDOMWindow.h"
 #include "core/frame/LocalFrame.h"
 #include "core/frame/Navigator.h"
 #include "core/frame/UseCounter.h"
@@ -81,6 +82,12 @@ bool NavigatorVibration::vibrate(Navigator& navigator, const VibrationPattern& p
     if (!frame->page()->isPageVisible())
         return false;
 
+    if (frame->isCrossOriginSubframe()) {
+        frame->localDOMWindow()->printErrorMessage(
+            "The cross-domain iframe is disallowed to call navigator.vibrate: https://www.chromestatus.com/feature/5682658461876224.");

[Nate Chapin, 2016/09/19 19:33:29]

"A cross-origin iframe may not call navigator.vibrate" is a little shorter and
clearer IMO.

+        return false;
+    }
+
     return NavigatorVibration::from(navigator).controller(*frame)->vibrate(pattern);
 }