Add deprecation warnings to old powerful features on insecure origins.

Source/modules/device_orientation/DeviceMotionController.cpp

Index: Source/modules/device_orientation/DeviceMotionController.cpp
diff --git a/Source/modules/device_orientation/DeviceMotionController.cpp b/Source/modules/device_orientation/DeviceMotionController.cpp
index d08247d32eb3e3b84e5882686623e27991e5215e..00f50502a8338c6b683f80e220c2fd7b5d490ef2 100644
--- a/Source/modules/device_orientation/DeviceMotionController.cpp
+++ b/Source/modules/device_orientation/DeviceMotionController.cpp
@@ -54,7 +54,7 @@ void DeviceMotionController::didAddEventListener(LocalDOMWindow* window, const A
         if (document().isPrivilegedContext(errorMessage)) {
             UseCounter::count(document().frame(), UseCounter::DeviceMotionSecureOrigin);
         } else {
-            UseCounter::count(document().frame(), UseCounter::DeviceMotionInsecureOrigin);
+            UseCounter::countDeprecation(document().frame(), UseCounter::DeviceMotionInsecureOrigin);

[timvolodine, 2015/04/30 10:47:45]

should there be a similar change in DeviceOrientationController.cpp? or is only
motion considered deprecated over non secure connections for now?

[jww, 2015/04/30 17:28:45]

Yes, it should. Done!

             if (document().frame()->settings()->strictPowerfulFeatureRestrictions())
                 return;
         }