[Webkit-unassigned] [Bug 84912] New: High res times should start at 0

[bugzilla-daemon at webkit.org]

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

           Summary: High res times should start at 0
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighR
                    esolutionTime/Overview.html
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: simonjam at chromium.org
                CC: tonyg at chromium.org, nduca at chromium.org,
                    sullivan at chromium.org


The spec has changed to define 0 as the value of navigationStart for the document. All times returned by window.performance.webkitNow() should be relative to that.

convertMonotonicTimeToDocumentTime() should automatically subtract off the value of navigationStart.

Note that doing so will break the time values returned by window.performance.timing. These values are supposed to use the monotonic clock, but not rebase their values to 0. To fix this, perhaps we could add a legacy accessor that doesn't subtract out navigationStart. This should be clearly marked as legacy, because all future uses are expected to use convertMonotonicTimeToDocumentTime().

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