Pass through geofencing API calls to the content layer.

Source/modules/geofencing/WorkerNavigatorGeofencing.h

Index: Source/modules/geofencing/WorkerNavigatorGeofencing.h
diff --git a/Source/modules/geofencing/WorkerNavigatorGeofencing.h b/Source/modules/geofencing/WorkerNavigatorGeofencing.h
new file mode 100644
index 0000000000000000000000000000000000000000..a2e36e98577b391a74b6d1b80f479358be5734f0
--- /dev/null
+++ b/Source/modules/geofencing/WorkerNavigatorGeofencing.h
@@ -0,0 +1,39 @@
+// 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 WorkerNavigatorGeofencing_h
+#define WorkerNavigatorGeofencing_h
+
+#include "platform/Supplementable.h"
+#include "platform/heap/Handle.h"
+
+namespace blink {
+
+class Geofencing;
+class WorkerNavigator;
+
+class WorkerNavigatorGeofencing FINAL
+    : public NoBaseWillBeGarbageCollectedFinalized<WorkerNavigatorGeofencing>

[jochen (gone - plz use gerrit), 2014/09/04 11:14:54]

nit. base classes should all go in one line, in line 16

[Marijn Kruisselbrink, 2014/09/04 17:44:19]

That doesn't actually seem to be a rule? And it's certainly not something that
is consistently adhered to in existing blink code (ServiceWorkerContainer,
ServiceWorkerContainerClient, ServiceWorkerRegistration and a bunch of other
classes all have one base class per line).

So am I now supposed to reformat all my code to follow this unwritten style rule
(including code like NavigatorGeofencing which isn't otherwise touched in this
CL)?

[jochen (gone - plz use gerrit), 2014/09/05 14:08:28]

Well, whenever I do a review, I ask for the code to be formatted like this. If
you go to the public/ directory for example, there's not a single example where
not all base classes are on one line
not in this CL, but please try to stick to it in the future

[Marijn Kruisselbrink, 2014/09/05 18:32:09]

It's just rather frustrating when different reviewers have different
(undocumented) coding styles they enforce. In public/ there is not a single
class with multiple inheritance, yes. In Source/, especially in the various more
recent modules, there are many classes with each base class on a separate line
(geolocation, indexeddb, mediasource, mediastream, netinfo, screen_orientation,
serviceworkers, vibration all have one base class per line for at least some of
their code).

+    , public WillBeHeapSupplement<WorkerNavigator> {
+    WILL_BE_USING_GARBAGE_COLLECTED_MIXIN(WorkerNavigatorGeofencing);
+

[jochen (gone - plz use gerrit), 2014/09/04 11:14:54]

nit wtf_make_noncopyable

[Marijn Kruisselbrink, 2014/09/04 17:44:19]

Done.

+public:
+    virtual ~WorkerNavigatorGeofencing();
+    static WorkerNavigatorGeofencing& from(WorkerNavigator&);
+
+    static Geofencing* geofencing(WorkerNavigator&);
+    Geofencing* geofencing();
+
+    virtual void trace(Visitor*) OVERRIDE;
+
+private:
+    WorkerNavigatorGeofencing();
+    static const char* supplementName();
+
+    PersistentWillBeMember<Geofencing> m_geofencing;
+};
+
+} // namespace blink
+
+#endif // WorkerNavigatorGeofencing_h