Move GeolocationDispatcher into blink.

third_party/WebKit/Source/modules/geolocation/Geolocation.cpp

Index: third_party/WebKit/Source/modules/geolocation/Geolocation.cpp
diff --git a/third_party/WebKit/Source/modules/geolocation/Geolocation.cpp b/third_party/WebKit/Source/modules/geolocation/Geolocation.cpp
index e23275993c4aafe13db18c74016de70ae3c97801..82bb87db32525650dfda89675ad6dd616a01b22a 100644
--- a/third_party/WebKit/Source/modules/geolocation/Geolocation.cpp
+++ b/third_party/WebKit/Source/modules/geolocation/Geolocation.cpp
@@ -93,6 +93,7 @@ Geolocation* Geolocation::create(ExecutionContext* context)
 Geolocation::Geolocation(ExecutionContext* context)
     : ActiveDOMObject(context)
     , m_geolocationPermission(PermissionUnknown)
+    , m_controller(new GeolocationController(this))

[Marijn Kruisselbrink, 2015/09/30 19:56:55]

Unless I'm missing something, the change to lifetime/ownership of
GeolocationController is completely unrelated to the changes in this CL?
It might definitely make sense to make such a change (and I think it might even
be mostly equivalent), but mixing the two refactors in one CL makes it a bit
hard to see which changes are for what reason.

I can think of a few reasons why you might have ended up mixing these two up,
but they're all for changes in behavior that should probably be separate CLs as
well.

Also this seems like it could be the cause of the layout tests you deleted no
longer passing?

[Sam McNally, 2015/10/01 01:54:50]

For a real CL it's worth splitting this up, but I think it's useful here for
examining how much simplification switching to mojo allows.
That test assumed all subframes shared a GeolocationClient with the parent
frame, which was only true due to the test setup.

[Marijn Kruisselbrink, 2015/10/01 03:36:09]

But changing the ownership and lifetime management for GeolocationController has
nothing whatsoever to do with switching to mojo. Both changes are completely
independent and by having them both in the CL it just becomes harder to see what
simplification switching to mojo allows.
Yes, and there is no reason to mix up changing that test setup with this CL. If
you keep GeolocationController to be tied to the Frame, you can keep using the
exact same test setup. No need to mix changing that part of the design and that
part of the test setup with the rest of this CL.

[Sam McNally, 2015/10/02 05:12:37]

Changing ownership of GeolocationController depends on switching to using mojo.
In fact, switching to mojo enables removing GeolocationController (and
GeolocationPosition) entirely.
The test change is independent of the change to GeolocationController ownership.
That test relied on the GeolocationClientMock being shared by
GeolocationControllers from different frames and being able to return cached
results synchronously. With the removal of GeolocationClient, this is no longer
possible.

 {
 }
 
@@ -108,6 +109,7 @@ DEFINE_TRACE(Geolocation)
     visitor->trace(m_pendingForPermissionNotifiers);
     visitor->trace(m_lastPosition);
     visitor->trace(m_requestsAwaitingCachedPosition);
+    visitor->trace(m_controller);
     ActiveDOMObject::trace(visitor);
 }
 
@@ -125,7 +127,7 @@ void Geolocation::stop()
 {
     LocalFrame* frame = this->frame();
     if (frame && m_geolocationPermission == PermissionRequested)
-        GeolocationController::from(frame)->cancelPermissionRequest(this);
+        m_controller->cancelPermissionRequest();
 
     // The frame may be moving to a new page and we want to get the permissions from the new page's client.
     m_geolocationPermission = PermissionUnknown;
@@ -136,11 +138,7 @@ void Geolocation::stop()
 
 Geoposition* Geolocation::lastPosition()
 {
-    LocalFrame* frame = this->frame();
-    if (!frame)
-        return 0;
-
-    m_lastPosition = createGeoposition(GeolocationController::from(frame)->lastPosition());
+    m_lastPosition = createGeoposition(m_controller->lastPosition());
 
     return m_lastPosition.get();
 }
@@ -467,14 +465,10 @@ void Geolocation::requestPermission()
     if (m_geolocationPermission != PermissionUnknown)
         return;
 
-    LocalFrame* frame = this->frame();
-    if (!frame)
-        return;
-
     m_geolocationPermission = PermissionRequested;
 
     // Ask the embedder: it maintains the geolocation challenge policy itself.
-    GeolocationController::from(frame)->requestPermission(this);
+    m_controller->requestPermission();
 }
 
 void Geolocation::makeSuccessCallbacks()
@@ -522,21 +516,13 @@ void Geolocation::setError(GeolocationError* error)
 
 bool Geolocation::startUpdating(GeoNotifier* notifier)
 {
-    LocalFrame* frame = this->frame();
-    if (!frame)
-        return false;
-
-    GeolocationController::from(frame)->addObserver(this, notifier->options().enableHighAccuracy());
+    m_controller->startUpdating(notifier->options().enableHighAccuracy());
     return true;
 }
 
 void Geolocation::stopUpdating()
 {
-    LocalFrame* frame = this->frame();
-    if (!frame)
-        return;
-
-    GeolocationController::from(frame)->removeObserver(this);
+    m_controller->stopUpdating();
 }
 
 void Geolocation::handlePendingPermissionNotifiers()