Re: [heycam/webidl] DOMTimeStamp confusion (#2)

Looking at users of this, I found:
* [Push API](https://www.w3.org/TR/push-api/#pushsubscription-interface)
* [GeoLocation](https://w3c.github.io/geolocation-api/#position_interface)
* [Digital goods](https://github.com/WICG/digital-goods/blob/main/explainer.md)
* [Storage buckets](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/buckets/storage_bucket.idl?q=DOMTimeStamp%20f:.idl&ss=chromium)
* [WebRTC](https://www.w3.org/TR/webrtc/#rtccertificateexpiration-dictionary)
* [Cookie Store](https://wicg.github.io/cookie-store/)
* [Notifications](https://notifications.spec.whatwg.org/#timestamp)
* [Handwriting recognition](https://github.com/WICG/handwriting-recognition)

Some of those seem pretty malleable still, but others are sufficiently baked in. At the same time, I'm not sure what breakage would look like if we switched them over to DOMHighResTimestamp, which is a double.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/2#issuecomment-909030799