@@ -227,8 +227,9 @@ <h3>Time Origin</h3>
227
227
< li > Assert that < var > global</ var > 's < a > time origin</ a > is not undefined.
228
228
</ li >
229
229
< li > Let < var > t1</ var > be the < a > DOMHighResTimeStamp</ a > representing the
230
- high resolution < a href ="https://en.wikipedia.org/wiki/Unix_time "> Unix
231
- time</ a > at which the < a > global monotonic clock</ a > is zero.
230
+ high resolution < a
231
+ data-cite ="ECMA-262#sec-time-values-and-time-range "> time</ a > at which
232
+ the < a > global monotonic clock</ a > is zero.
232
233
</ li >
233
234
< li > Let < var > t2</ var > be the < a > DOMHighResTimeStamp</ a > representing the
234
235
high resolution time value of the < a > global monotonic clock</ a > at < var >
@@ -310,8 +311,8 @@ <h3>Monotonic Clock</h3>
310
311
getting < code > < a > performance.timeOrigin</ a > </ code > MUST use the same
311
312
< dfn > global monotonic clock</ dfn > that is shared by < a > time origin</ a > 's,
312
313
is monotonically increasing and not subject to system clock adjustments or
313
- system clock skew, and whose reference point is the Unix time—see < a href =
314
- "#sec-privacy-security "> </ a > .</ p >
314
+ system clock skew, and whose reference point is the [[ECMA-262]] time
315
+ definition - see < a href = "#sec-privacy-security "> </ a > .</ p >
315
316
< p class ="note "> The user agent can reset its global monotonic clock across
316
317
browser restarts, or whenever starting an isolated browsing session—e.g.
317
318
incognito or similar browsing mode. As a result, developers should not use
@@ -370,11 +371,11 @@ <h3>Clock drift</h3>
370
371
exposes a < a > global monotonic clock</ a > to the application, and that must
371
372
be shared across all the browser contexts. The < a > global monotonic
372
373
clock</ a > does not need to be tied to physical time, but is recommended
373
- to be set with respect to the < a href =
374
- " https://en.wikipedia.org/wiki/Unix_time " > Unix time</ a > to avoid exposing
375
- new fingerprint entropy about the user— e.g. this time can already be
376
- easily obtained by the application, whereas exposing a new logical clock
377
- provides new information.</ p >
374
+ to be set with respect to the [[ECMA-262]] definition of < a
375
+ data-cite =" ECMA-262#sec-time-values-and-time-range " > time</ a > to avoid
376
+ exposing new fingerprint entropy about the user — e.g. this time can
377
+ already be easily obtained by the application, whereas exposing a new
378
+ logical clock provides new information.</ p >
378
379
< p > However, even with above mechanism in place, the < a > global monotonic
379
380
clock</ a > may provide additional < a href =
380
381
"https://en.wikipedia.org/wiki/Clock_drift "> clock drift</ a > resolution.
0 commit comments