- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Nov 2021 13:51:03 +0000
- To: public-webrtc-logs@w3.org
When looking more carefully at the code, I found that EpochTimeStamp (old DOMTimeStamp) was used in 2 places, one as a relative time (when setting cert expiry) and one as an absolute time (when showing a certificate). So one needs to be EpochTimeStamp and the other needs to be DOMHighResTimeStamp. DOMHighResTimeStamp do have a defined origin (the page load time, roughly), but the difference between page load time and "now" (our previous interpretation) should be small enough not to matter in most cases. A compatibility note may be nice. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2674#issuecomment-975545173 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 November 2021 13:51:11 UTC