[sensors]: Introduce the Generic Sensor API.

third_party/WebKit/Source/modules/sensor/SensorReading.idl

Index: third_party/WebKit/Source/modules/sensor/SensorReading.idl
diff --git a/third_party/WebKit/Source/modules/sensor/SensorReading.idl b/third_party/WebKit/Source/modules/sensor/SensorReading.idl
new file mode 100644
index 0000000000000000000000000000000000000000..37833c74e397b237076ce058088721d343f670b8
--- /dev/null
+++ b/third_party/WebKit/Source/modules/sensor/SensorReading.idl
@@ -0,0 +1,13 @@
+// Copyright 2016 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.
+
+// Specification at:
+// https://w3c.github.io/sensors/#sensorreading1
+
+[
+    Constructor(),
+    RuntimeEnabled=Sensor,
+] interface SensorReading {
+    readonly attribute DOMHighResTimeStamp timeStamp;

[timvolodine, 2016/05/06 17:04:30]

I assume concrete sensors would derive from SensorReading. However do we always
need a timeStamp? looks like can be potentially overhead for very hi-frequency
sensors. Maybe it should be nullable or not there at all?

[riju_, 2016/05/12 14:12:46]

Spec issue raised it in https://github.com/w3c/sensors/issues/105

+};