Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Refer to ECMA-262 time rather than unix time #66

Merged
merged 3 commits into from Apr 23, 2019
Merged

Refer to ECMA-262 time rather than unix time #66

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fad3047
Refer to ECMA-262 time rather than unix time
yoavweiss Apr 23, 2019
00775da
Update index.html
marcoscaceres Apr 23, 2019
8edb0f6
Update index.html
marcoscaceres Apr 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 10 additions & 9 deletions index.html
View file
Open in desktop
Expand Up @@ -227,8 +227,9 @@ <h3>Time Origin</h3>
<li>Assert that <var>global</var>'s <a>time origin</a> is not undefined.
</li>
<li>Let <var>t1</var> be the <a>DOMHighResTimeStamp</a> representing the
high resolution <a href="https://en.wikipedia.org/wiki/Unix_time">Unix
time</a> at which the <a>global monotonic clock</a> is zero.
high resolution <a
data-cite="ECMA-262#sec-time-values-and-time-range">time</a> at which
the <a>global monotonic clock</a> is zero.
</li>
<li>Let <var>t2</var> be the <a>DOMHighResTimeStamp</a> representing the
high resolution time value of the <a>global monotonic clock</a> at <var>
Expand Down Expand Up @@ -310,8 +311,8 @@ <h3>Monotonic Clock</h3>
getting <code><a>performance.timeOrigin</a></code> MUST use the same
<dfn>global monotonic clock</dfn> that is shared by <a>time origin</a>'s,
is monotonically increasing and not subject to system clock adjustments or
system clock skew, and whose reference point is the Unix time—see <a href=
"#sec-privacy-security"></a>.</p>
system clock skew, and whose reference point is the ECMA-262 time
yoavweiss marked this conversation as resolved.
Show resolved Hide resolved
definition - see <a href= "#sec-privacy-security"></a>.</p>
<p class="note">The user agent can reset its global monotonic clock across
browser restarts, or whenever starting an isolated browsing session—e.g.
incognito or similar browsing mode. As a result, developers should not use
Expand Down Expand Up @@ -370,11 +371,11 @@ <h3>Clock drift</h3>
exposes a <a>global monotonic clock</a> to the application, and that must
be shared across all the browser contexts. The <a>global monotonic
clock</a> does not need to be tied to physical time, but is recommended
to be set with respect to the <a href=
"https://en.wikipedia.org/wiki/Unix_time">Unix time</a> to avoid exposing
new fingerprint entropy about the user—e.g. this time can already be
easily obtained by the application, whereas exposing a new logical clock
provides new information.</p>
to be set with respect to the ECMA-262 definition of <a
yoavweiss marked this conversation as resolved.
Show resolved Hide resolved
data-cite="ECMA-262#sec-time-values-and-time-range">time</a> to avoid
exposing new fingerprint entropy about the user — e.g. this time can
already be easily obtained by the application, whereas exposing a new
logical clock provides new information.</p>
<p>However, even with above mechanism in place, the <a>global monotonic
clock</a> may provide additional <a href=
"https://en.wikipedia.org/wiki/Clock_drift">clock drift</a> resolution.
Expand Down