-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alias performance.now to date.now #2952
Comments
https://core.ac.uk/download/pdf/80792157.pdf Possibly of interest |
It seems like HR timers don't provide very much value at all. We should probably disable them, or at least substantially decrease their granularity. |
Plan of record: disable. |
I'm going to close this. I think HR timers are probably more bad than good for the web platform, but we dont have any serious plans to actually remove these, and FF is re-enabling, and there are definitely much bigger priorities for us privacy / security wise. Since this is all but guaranteed to never be acted on, im going to pull-the-bandaid-off and just close it |
Description
HR-Timers have been implemented in various browsers to provide higher precision timing information for various tasks like script execution and resource fetches. Opening the issue to investigate the fingerprinting risk associated with this API.
https://w3c.github.io/hr-time/#sec-privacy-security
https://www.w3.org/TR/navigation-timing-2/#security
cc: @snyderp
The text was updated successfully, but these errors were encountered: