Add GeolocationManager service

device/geolocation/public/interfaces/geolocation_config.mojom

Index: device/geolocation/public/interfaces/geolocation_config.mojom
diff --git a/device/geolocation/public/interfaces/geolocation_config.mojom b/device/geolocation/public/interfaces/geolocation_config.mojom
new file mode 100644
index 0000000000000000000000000000000000000000..e48d8a5c4ab7cf5b0bfa0db133b7ce80186f0444
--- /dev/null
+++ b/device/geolocation/public/interfaces/geolocation_config.mojom
@@ -0,0 +1,13 @@
+// Copyright 2017 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.
+
+module device.mojom;
+
+// Provides an interface for browser process to access geolocation capturing

[Ken Rockot(use gerrit already), 2017/07/12 18:19:32]

I think it's wrong to refer to "browser process" in a device service mojom, but
perhaps this is just another symptom of the more general problem of security
review being more difficult in a mojom world. Fine for now I guess.

[blundell, 2017/07/13 11:30:15]

I agree with Ken. The Device Service is conceptually below a concept like the
browser process. As a compromise, could we write something like

"for trusted clients (e.g., the browser process in Chrome)"

?

+// config.
+interface GeolocationConfig {
+  // Returns true if the location is being captured and high_accurary is

[estark, 2017/07/12 18:11:51]

typo: high_accuracy

[asimjour1, 2017/07/12 21:58:20]

Done.

+  // enabled.
+  IsHighAccuracyLocationBeingCaptured() => (bool high_accuracy);
+};