Pass through geofencing API calls to the browser process.

content/child/blink_platform_impl.cc

Index: content/child/blink_platform_impl.cc
diff --git a/content/child/blink_platform_impl.cc b/content/child/blink_platform_impl.cc
index 54e23eca45acdf9dd2142e53fa79b63364ce56f3..5e9ca691c5ab7db51f00452fab0a417d728f5d76 100644
--- a/content/child/blink_platform_impl.cc
+++ b/content/child/blink_platform_impl.cc
@@ -32,6 +32,7 @@
 #include "content/child/child_thread.h"
 #include "content/child/content_child_helpers.h"
 #include "content/child/fling_curve_configuration.h"
+#include "content/child/geofencing/web_geofencing_provider_impl.h"
 #include "content/child/web_discardable_memory_impl.h"
 #include "content/child/web_socket_stream_handle_impl.h"
 #include "content/child/web_url_loader_impl.h"
@@ -406,7 +407,13 @@ BlinkPlatformImpl::BlinkPlatformImpl()
       shared_timer_fire_time_was_set_while_suspended_(false),
       shared_timer_suspended_(0),
       fling_curve_configuration_(new FlingCurveConfiguration),
-      current_thread_slot_(&DestroyCurrentThread) {}
+      current_thread_slot_(&DestroyCurrentThread) {
+  // ChildThread may not exist in some tests.
+  if (ChildThread::current()) {
+    web_geofencing_provider_.reset(new WebGeofencingProviderImpl(
+        ChildThread::current()->thread_safe_sender()));
+  }
+}
 
 BlinkPlatformImpl::~BlinkPlatformImpl() {
 }
@@ -991,6 +998,9 @@ blink::WebCrypto* BlinkPlatformImpl::crypto() {
   return &web_crypto_;
 }
 
+blink::WebGeofencingProvider* BlinkPlatformImpl::geofencingProvider() {
+  return web_geofencing_provider_.get();

[jochen (gone - plz use gerrit), 2014/09/11 12:47:27]

how will you test the feature in layout tests?

[Marijn Kruisselbrink, 2014/09/11 17:57:52]

To be honest I have no idea. The actual feature I'll probably be able to test
with unittests purely on the browserside, which should test 99% of the
functionality since API calls are passed on more or less unmodified. But I'm not
sure how I would test the other 1% to make sure things are passed around
correctly. Any suggestions are welcome.

[jochen (gone - plz use gerrit), 2014/09/12 13:52:54]

having a closer look, this should probably be in content/renderer's of the blink
platform (which derives from this class).

It has a bunch of hooks to install a mock here. the mock would exist in
content/shell/renderer (see for example the geolocation stuff)

+}
 
 WebThemeEngine* BlinkPlatformImpl::themeEngine() {
   return &native_theme_engine_;