Blink side of exposing the service worker registration associated with geofencing API calls.

Source/modules/geofencing/WorkerNavigatorGeofencing.cpp

Index: Source/modules/geofencing/WorkerNavigatorGeofencing.cpp
diff --git a/Source/modules/geofencing/WorkerNavigatorGeofencing.cpp b/Source/modules/geofencing/WorkerNavigatorGeofencing.cpp
index 5b3928cd58aeec8a1690f1f8f5ec1b7a6c32e356..1d5394f3b7653dd9c7df95168174cd9ebf44f8c3 100644
--- a/Source/modules/geofencing/WorkerNavigatorGeofencing.cpp
+++ b/Source/modules/geofencing/WorkerNavigatorGeofencing.cpp
@@ -41,7 +41,7 @@ Geofencing* WorkerNavigatorGeofencing::geofencing(WorkerNavigator& navigator)
 Geofencing* WorkerNavigatorGeofencing::geofencing()
 {
     if (!m_geofencing)
-        m_geofencing = Geofencing::create();
+        m_geofencing = Geofencing::create(nullptr);

[michaeln, 2014/10/14 01:16:16]

maybe add a FIXME here about passing in the registration for |this| service
worker context?

[Marijn Kruisselbrink, 2014/10/14 18:21:07]

Well, when the registration is accessible from the service worker itself, this
entire class can go away since then the geofencing API is reachable through that
ServiceWorkerRegistration instance (hence the FIXME: delete this class I added
to the header and idl files).

     return m_geofencing.get();
 }