Search results

Describe the risk of exposing additional hardware clocks

Status: Open.

#164 In w3c/hr-time;

· jyasskin opened on Oct 16, 2023

Why is EpochTimeStamp discouraged?

Status: Open.

#149 In w3c/hr-time;

· domenic opened on Feb 15, 2023

<code>timeOrigin</code> and skew over time from the system clock

Status: Open.

#141 In w3c/hr-time;

· yoavweiss opened on Dec 8, 2022

Cross-Origin Isolation in S&amp;P section

Status: Open.

#128 In w3c/hr-time;

· yoavweiss opened on Sep 1, 2021

Suggestions: ticking during sleep, comparison across contexts, time origin + now semantics, and skew definition

Status: Open.

#115 In w3c/hr-time;

· jonathanmayer opened on May 6, 2021

Add description of various timer related vulnerabilities to the security and privacy sections

hackathon_2020

Status: Open.

#102 In w3c/hr-time;

· yoavweiss opened on Oct 6, 2020

Security and privacy considerations for DOMHighResTimeStamp resolution

privacy-trackerGroup bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.

security-trackerGroup bringing to attention of security, or tracked by the security Group but not needing response.Group bringing to attention of security, or tracked by the security Group but not needing response.

Status: Open.

#79 In w3c/hr-time;

· igrigorik opened on Jul 2, 2019