Consider using DOMHighResTimestamp instead of DOMTimeStamp

[yoavweiss]

We're considering our options RE DOMTimeStamp, and wondering what it's used for. It seems less well-defined than DOMHighResTimestamp. Would y'all consider switching over?

See whatwg/webidl#2 for discussion.

[marcoscaceres]

We probably can’t switch because of web compat. It’s used to determine the age of the acquired position.

But we could rename it LegacyGeolocationTimeStamp as it’s just a typedef and define it as used by the API. That could finally deprecating it from the platform.

[yoavweiss]

Geolocation is not the only user today. Agree that renaming it may prevent new users though.

[marcoscaceres]

Ah, my bad. Those WICG ones should be easy to update at least.

[npm1]

Compat aside, looks like DOMTimeStamp (or now EpochTimeStamp) introduce high resolution timers (there's not clamping whatsoever), so for privacy/security they should probably move?

[npm1]

Nevermind, Yoav mentioned this is an int so the granularity is not sub-ms.