Remove DOMTimeStamp

[marcoscaceres]

Closes #2

DOMTimeStamp becomes EpochTimeStamp in HR-TIME.
w3c/hr-time#124

Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1735096

---

Preview | Diff

[marcoscaceres]

EpochTimeStamp is now in HR-Time.

[marcoscaceres]

Filed meta Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1735096 ... along with various dependent changes.

[marcoscaceres]

WebKit has implemented EpochTimeStamp (and removed DOMTimeStamp): https://bugs.webkit.org/show_bug.cgi?id=231496

[marcoscaceres]

Chromium is also in the process of being updated: https://bugs.chromium.org/p/chromium/issues/detail?id=1258466

[domenic]

Looks like all uses have been eliminated! https://dontcallmedom.github.io/webidlpedia/names/DOMTimeStamp.html

[dontcallmedom]

given dontcallmedom/webidlpedia#24, here is the list of remaining DOMTimeStamp mentions:

• Notification.timestamp in Notifications (and matching field in NotificationOptions)
• CookieStore as discussed in Consider using DOMHighResTimestamp instead of DOMTimeStamp WICG/cookie-store#205
• RTCCertificateExpiration.expires and RTCCertificate.expires in WebRTC - tracked in Consider using DOMHighResTimestamp instead of DOMTimeStamp w3c/webrtc-pc#2674

[domenic]

Thank you, @dontcallmedom!

Do people think we should revert this for now, since some of those discussions are still ongoing? Or just try to forge ahead? I'll file a Notifications API issue...

[marcoscaceres]

Personally, I think we should forge ahead. Changes have landed in WebKit, there are patches really close to landing in Gecko, and bugs have been filed on Chromium (not sure about the status of the implementation tho).

[marcoscaceres]

Sent PR to WebRTC.