{"action":"opened","issue":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/309","labels_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/309/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/309/comments","events_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/309/events","html_url":"https://github.com/w3c/webrtc-pc/issues/309","id":107601700,"number":309,"title":"Use of DOMHiResTimestamp in Section 8.5","user":{"login":"aboba","id":808811,"avatar_url":"https://avatars.githubusercontent.com/u/808811?v=3","gravatar_id":"","url":"https://api.github.com/users/aboba","html_url":"https://github.com/aboba","followers_url":"https://api.github.com/users/aboba/followers","following_url":"https://api.github.com/users/aboba/following{/other_user}","gists_url":"https://api.github.com/users/aboba/gists{/gist_id}","starred_url":"https://api.github.com/users/aboba/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aboba/subscriptions","organizations_url":"https://api.github.com/users/aboba/orgs","repos_url":"https://api.github.com/users/aboba/repos","events_url":"https://api.github.com/users/aboba/events{/privacy}","received_events_url":"https://api.github.com/users/aboba/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-21T21:26:20Z","updated_at":"2015-09-21T21:26:20Z","closed_at":null,"body":"DOMHiResTimeStamp is used in the Stats API Section 8.5:  \r\n\r\ndictionary RTCStats {\r\n             DOMHiResTimeStamp timestamp;\r\n             RTCStatsType      type;\r\n             DOMString         id;\r\n};\r\n\r\nHarald has noted the following issues with this: \r\n\r\n\"The use of DOMHiResTimeStamp is actually troubling, for multiple reasons, none of which is actually a technical concern:\r\n\r\n1) The name is wrong. It's DOMHighResTimeStamp.\r\n\r\n2) The definition (which is a typedef for Double) states that \"The DOMHighResTimeStamp type is used to store a time value measured relative to the navigationStart attribute of the PerformanceTiming interface [NavigationTiming], the start of navigation of the document, or a time value that represents a duration between two DOMHighResTimeStamps.\"\r\n\r\nIt also says that \"The time values returned when calling the now method MUST be monotonically increasing and not subject to system clock adjustments or system clock skew. The difference between any two chronologically recorded time values returned from the now method MUST never be negative.\" Not normative for our usage, but might surprise some.\r\n\r\nBoth of these are troublesome given that\r\nthey don't seem to admit of an implementation that uses the system clock's idea of time relative to Jan 1, 1970.\r\nWe can do it, but it's a novel usage of the type.\"\r\n\r\n\r\n\r\n"}}