[sensors] Introduce Generic Sensor API interfaces

content/browser/BUILD.gn

Index: content/browser/BUILD.gn
diff --git a/content/browser/BUILD.gn b/content/browser/BUILD.gn
index e0bc7d1ec6311cf06191245c28051fd67c40265b..4c3819d97db14cbc96ae55f960499f636c87380c 100644
--- a/content/browser/BUILD.gn
+++ b/content/browser/BUILD.gn
@@ -62,6 +62,7 @@ source_set("browser") {
     "//device/battery",
     "//device/bluetooth",
     "//device/gamepad",
+    "//device/generic_sensor",

[timvolodine, 2016/08/18 22:52:13]

we may want to have "enable_generic_sensor" for this (as e.g. enable_webrtc)?
(to allow control for smaller chrome/webview footprint)

[Mikhail, 2016/08/19 09:29:55]

We'd like to keep it as a runtime-enabled feature, so that try bots can compile
the code, and developers can easily enable it and provide early feedback for the
new API..

[timvolodine, 2016/08/19 16:02:30]

This would allow to enable on platform by platform basis when actual platform
implementations are available. There is not much to feedback on if there is no
implementation for a particular platform ;)

I don't feel strongly about this though, guess android would be the most
footprint-sensistive.

     "//device/geolocation:device_geolocation",
     "//device/geolocation/public/interfaces",
     "//device/power_save_blocker",