UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.2999.0 Safari/537.36
Steps to reproduce the problem:
1. http://w3c-test.org/hr-time/window-worker-time-origin.html
What is the expected behavior?
Expected performance.now() in the Worker to be close to the Worker's moment of creation.
What went wrong?
performance.now() was relative to the Window's time origin, instead of the Worker.
Did this work before? No
Does this work in other browsers? Yes (WebKit Nightly)
Chrome version: 58.0.2999.0 Channel: canary
OS Version: OS X 10.12.4
Flash Version:
See: https://github.com/w3c/hr-time/issues/41
Spec: https://w3c.github.io/hr-time/#time-origin-1
Labels: OS-Android OS-Chrome OS-Linux OS-Windows Status: Available (was: Unconfirmed)
The spec of time origin of dedicated worker has changed in Feb 2015 (see https://github.com/w3c/hr-time/issues/1), but we haven't updated our implementation.
We have to implement performance.timeOrigin attribute as well so that users can translate timestamps across contexts.
Comment 1 by ksakamoto@chromium.org
, Feb 3 2017Status: Available (was: Unconfirmed)