From 220650036961eecb29c06c23b010d31afde3641f Mon Sep 17 00:00:00 2001 From: Steve Block Date: Fri, 25 May 2012 18:37:59 +0100 Subject: Make sure we don't use GPS when not required This makes sure that we disable the GPS if a single page makes requests with enableHighAccuracy enabled, followed by requests with enableHighAccuracy disabled. Bug: 6511338 Change-Id: I4d67b84d5eed04822c05f70c2dce47a5a696c2fc --- Source/WebKit/android/WebCoreSupport/GeolocationClientImpl.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'Source/WebKit') diff --git a/Source/WebKit/android/WebCoreSupport/GeolocationClientImpl.cpp b/Source/WebKit/android/WebCoreSupport/GeolocationClientImpl.cpp index 4e53d08..6291b7d 100644 --- a/Source/WebKit/android/WebCoreSupport/GeolocationClientImpl.cpp +++ b/Source/WebKit/android/WebCoreSupport/GeolocationClientImpl.cpp @@ -122,6 +122,7 @@ void GeolocationClientImpl::stopUpdating() { // TODO: It would be good to re-use the Java bridge object. m_javaBridge.clear(); + m_useGps = false; // Reset last position and error to make sure that we always try to get a // new position from the client when a request is first made. m_lastPosition = 0; -- cgit v1.1