Removal of geolocation APIs on insecure origins

third_party/WebKit/Source/core/frame/UseCounter.cpp

Index: third_party/WebKit/Source/core/frame/UseCounter.cpp
diff --git a/third_party/WebKit/Source/core/frame/UseCounter.cpp b/third_party/WebKit/Source/core/frame/UseCounter.cpp
index 6397d00f9f7fc8b5ef2d46c483ef779d2bff9314..84b1946320acaf9fa7ea188e06a20d5472a4c2ab 100644
--- a/third_party/WebKit/Source/core/frame/UseCounter.cpp
+++ b/third_party/WebKit/Source/core/frame/UseCounter.cpp
@@ -877,7 +877,7 @@ String UseCounter::deprecationMessage(Feature feature)
         return "The deviceorientationabsolute event is deprecated on insecure origins, and support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.";
 
     case GeolocationInsecureOrigin:
-        return "getCurrentPosition() and watchPosition() are deprecated on insecure origins, and support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.";
+        return "getCurrentPosition() and watchPosition() no longer work on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.";

[Torne, 2016/01/05 11:21:23]

I'm not clear on how the warnings work here, so one question: after this change
lands, will there still be a warning printed to the console in WebView apps
which use geolocation on insecure origins? If so, does this mean the wording of
the warning has changed to say that it doesn't work even though it still does?

[jww, 2016/01/06 02:40:59]

Indeed, you are correct. How about I change the wording to be a bit more
ambiguous for now (see the new CL), and we can change it to be more explicitly
"no longer work" after WebView is fixed permanently?

 
     case GetUserMediaInsecureOrigin:
         return "getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.";