time origin should be equivalent to performance.timing.navigationStart

Confirmed Issue #7167808 • Assigned to Todd R.


Majid V.
Apr 11, 2016
This issue is public.
Found in
  • Microsoft Edge
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

According to the spec the time origin for high resolution timestamp should be equivalent to |performance.timing.navigationStart| (at least when navigating between two documents).
This means that I expect the following expression to have an absolute value that is smaller than 2ms (1ms = rounding error upper bound + 1m ~ cost of calling and
|( - performance.timing.navigationStart) -|
In my tests I see a varying value that goes up to 15ms in EdgeHTML. This is unexpected and I believe is incorrect. This simple test page shows this (let it run for multiple reloads to see the effect).
See attached screenshot showing Firefox, Edge, Chrome running the above page on Win 10. Note that I have noticed occasionally an incorrect value in Chrome as well but that is also likely a bug in Chrome as well.
P.S. I originally filed this in old bug tracker but it was closed as I didn’t provide feedback in time. The fact that this issue is happening in Chrome does not actually mean it is not a bug. Unless my reading of the spec is inaccurate.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Travis L.”

    Changed Assigned To from “Travis L.” to “Ibrahim O.”

    Changed Assigned To to “Travis L.”

    Changed Assigned To to “Rico M.”

    Changed Assigned To from “Rico M.” to “Todd R.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Todd R.” to “Justin R.”

    Changed Assigned To from “Justin R.” to “Todd R.”

  • I agree with the semantices behind this bug however… fixing this will require some communication with other vendors… as ECMAScript and W3C HR-Time specs are not currently related. This means it is possible for's version of time since 1970 to differ from performance.


    I’ve opened for us to track an open discussion of this within the W3C Web Performance Working Group. After that issue is resolved, we will look into aligning Microsoft Edge with that decision.

You need to sign in to your Microsoft account to add a comment.

Sign in