- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Jan 2018 16:49:54 +0000
- To: public-webrtc-logs@w3.org
> define these timestamps in reference to the context's global monotonic clock > ... prefer to have something that gives "something like the wall clock" @alvestrand It sounds like you want a timestamp that's comparable to ```js performance.timing.navigationStart + performance.now() ``` Is that correct? > you better not be comparing it to Date.now() even though it'll be really tempting! As @bzbarsky points out, [a bit of a footgun](https://jsfiddle.net/jib1/zqpo4kcq/), but an improvement over *getStats*'s timestamp today, and more backwards compatible than say, changing its (zero-)origin from 1970 to page load. I like it, if we can move both *getStats* and *getContributingSources/getSynchronizationSources* to it. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1690#issuecomment-356343524 using your GitHub account
Received on Tuesday, 9 January 2018 16:49:57 UTC