[Webkit-unassigned] [Bug 84914] New: [Chromium] Need to expose TimeTicks::HighResNow()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=84914

           Summary: [Chromium] Need to expose TimeTicks::HighResNow()
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: simonjam at chromium.org
                CC: jamesr at chromium.org, tonyg at chromium.org,
                    nduca at chromium.org, sullivan at chromium.org


In order to properly implement window.performance.now(), we need a sub-millisecond timer. Currently, we return TimeTicks::Now(). On Windows, that only has (at best) a 1 ms resolution. We need to instead use TimeTicks::HighResNow() to get microsecond resolution. Note the warnings in time_win.cc that HighResNow() is slower and not always available. For some users, they'll never get better that tick resolution (1 - 15 ms).

This should probably be plumbed through via monotonicallyIncreasingTime().

We should also be careful to ensure that TimeTicks::Now() and TimeTicks::HighResNow() use the same time base. The network times that are used for Navigation Timing are passed in by calling TimeTicks::Now() in the browser process.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.