- From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Oct 2015 09:03:01 +0000
- To: public-webtiming@w3.org
In accordance with above considerations I've updated the spec to
define the internal clock of the timing object to be representing
seconds - not milliseconds.
```js
var clock = function () {return performance.now()/1000.0;}
```
I have also emphasized that all time values mentioned in the spec are
seconds, including timestamps in statevectors and skew estimates.
--
GitHub Notif of comment by ingararntzen
See
https://github.com/webtiming/timingobject/issues/17#issuecomment-149151795
Received on Monday, 19 October 2015 09:03:05 UTC