Tom Ritter 5660579449 Bug 1440195 For timestamps that are absolute, specify a null context pointer r=baku ...

Note that by not using the same context pointer for all timestamps within a single
'communication group' (that is, all things that can communication to each other
in JavaScript), it's possible to observe time going backwards.

Imagine comparing
  performance.timeOrigin + performance.now() < new File([], "").lastModified

In theory this should always be true. However, if performance.now() was jittered
up (using one context pointer, because it is a relative timestamp) and File was
jittered down (using a null context pointer, because it is an absolute timestamp)
then this may evaluate to False.

I think this is okay.

MozReview-Commit-ID: BfgbmGS8XdD

2018-02-28 15:37:26 -06:00

3.3 KiB

Raw Blame History

View Raw