Pass through geofencing API calls to the content layer.

public/platform/WebCircularRegion.h

+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef WebCircularRegion_h
+#define WebCircularRegion_h
+
+#include "WebCommon.h"
+#include "WebGeofencingRegion.h"
+#include "WebPrivatePtr.h"
+
+namespace blink {
+
+class WebCircularRegionPrivate;
+
+class WebCircularRegion : public WebGeofencingRegion {

[esprehn, 2014/08/19 01:15:59]

FINAL

[Marijn Kruisselbrink, 2014/08/19 18:55:14]

Done.

+public:
+    WebCircularRegion(const WebCircularRegion& other) { assign(other); }
+    WebCircularRegion& operator=(const WebCircularRegion& other)
+    {
+        assign(other);
+        return *this;
+    }
+
+    BLINK_PLATFORM_EXPORT static WebCircularRegion create(const WebString& id, double latitude, double longitude, double radius);
+
+    BLINK_PLATFORM_EXPORT double latitude() const;
+    BLINK_PLATFORM_EXPORT double longitude() const;
+    BLINK_PLATFORM_EXPORT double radius() const;
+
+private:
+    friend class WebGeofencingRegion;

[esprehn, 2014/08/19 01:15:59]

Why do you need friends?

[Marijn Kruisselbrink, 2014/08/19 18:55:14]

because WebGeofencingRegion::to and constTo create null instances before
assigning a value. But there really is no reason for that constructor to be
private, which eliminates the need for the friend.

+
+    WebCircularRegion() { }
+
+    WebCircularRegionPrivate* privateData() const;
+};
+
+} // namespace blink
+
+#endif // WebCircularRegion_h