Eventually rename the SensorReading timeStamp attribute for consistency with DOM events. #101
Comments
|
is having a timeStamp for reading really needed? I imagine this can be unnecessary for very hi-freq sensors. Maybe at least it should be nullable? |
|
Yeah, timeStamps are the only means to compute both latency and frequency. |
|
@timvolodine, I saw @riju opened a dedicated issue for exposing the timestamp in #105. Let's continue that specific conversation there. |
tobie
added a commit
to tobie/sensors
that referenced
this issue
Jan 26, 2017
This fixes a number of pending issues listed below, for which there was consensus, but editing was still pending. This introduces a dependency on the infra standard [[INFRA]], to define precisely the low-level data structures used by slots and concepts. This also specifies slots more clearly. Additionally, this rewrite sprinkles inline issues in areas of the specs which require more work. * Handle GC issues by getting rid of the SensorReading interface. Closes w3c#153. Closes w3c#101. * Check sensor existence before requesting permission. Closes w3c#145. * Remove side effects from constructors. Closes w3c#138. * Move default sensor check to start() and add "unconnected" state. Closes w3c#128 and closes w3c#104. * Throttle update frequency to 60Hz by relying on requestAnimationFrame. Closes w3c#100.
tobie
added a commit
that referenced
this issue
Jan 26, 2017
This fixes a number of pending issues listed below, for which there was consensus, but editing was still pending. This introduces a dependency on the infra standard [[INFRA]], to define precisely the low-level data structures used by slots and concepts. This also specifies slots more clearly. Additionally, this rewrite sprinkles inline issues in areas of the specs which require more work. * Handle GC issues by getting rid of the SensorReading interface. Closes #153. Closes #101. * Check sensor existence before requesting permission. Closes #145. * Remove side effects from constructors. Closes #138. * Move default sensor check to start() and add "unconnected" state. Closes #128 and closes #104. * Throttle update frequency to 60Hz by relying on requestAnimationFrame. Closes #100.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The DOM standard wants events to expose a
DOMHighResTimestamptime stamp. It's up for debate right now whether it would be Web-compatible to modify thetimeStampattribute or whether a new attribute needs to be added to the spec instead.For consistency,
SensorReadingtimeStampattribute, which is aDOMHighResTimestamp, will be renamed to whatever ends up being chosen for events.The text was updated successfully, but these errors were encountered: