- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 21:59:14 +0000
- To: public-webrtc-logs@w3.org
The WebRTC spec mentions DOMTimeStamp five times, all in the context of the "expires" timestamp on the RTCCertificate. It also mentions DOMHighResTimestamp five times, covering RTCStats and RTCRtpContributingSource. WebCrypto does not specify how the expiration date of an attribute should be specified, so its interpretation is clearly a WebRTC only matter, and the text clearly indicates that it was taken to be a time offset relative to "now" (it says that the value 2592000000 represents an expiry time of 30 days in the future). I would not at all mind using DOMHighResTimestamp instead if that's a compatible spec change (meaning that users wouldn't have to modify their code). -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2674#issuecomment-912088117 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 21:59:16 UTC