Pass through the geofencing API calls to the content layer.

public/web/WebFrameClient.h

Index: public/web/WebFrameClient.h
diff --git a/public/web/WebFrameClient.h b/public/web/WebFrameClient.h
index 0c570f530b590dbb6643901f7f7377b2c8812d14..c5111872eccf3e30bc7d5b2909c328a4e627121f 100644
--- a/public/web/WebFrameClient.h
+++ b/public/web/WebFrameClient.h
@@ -63,6 +63,7 @@ class WebCookieJar;
 class WebDataSource;
 class WebDOMEvent;
 class WebFormElement;
+class WebGeofencingClient;
 class WebGeolocationClient;
 class WebInputEvent;
 class WebMediaPlayer;
@@ -465,6 +466,9 @@ public:
     // Access the embedder API for (client-based) geolocation client .
     virtual WebGeolocationClient* geolocationClient() { return 0; }
 
+    // Access the embedder API for geofencing client.
+    virtual WebGeofencingClient* geofencingClient() { return 0; }

[Peter Beverloo, 2014/07/14 17:23:09]

The geofencing client defines methods for (un)registering and getting a list of
registered regions. By plumbing these through WebFrame, the client will only be
available for Document contexts, and thus not for Worker contexts.

Given that the primary power of Geofencing can be found in workers, this doesn't
make sense. Instead, these calls should go through the Platform class, which
isn't related to any specific Frame/View.

+
 
     // MediaStream -----------------------------------------------------