Closed jyggen closed 7 years ago
I do not see this behaviour with current code. Which Chrome version you are testing with? PHP version and server OS might be useful too.
Updated my Chrome. Seems behaviour has changed between 57 and 58. Thanks for the heads up!
Related Chromium issue: https://codereview.chromium.org/2689833002
The current code, which uses seconds in the header, results in some strange timings in (at least) Chrome's dev tools. It seems like milliseconds is what's expected.
Before (using
$seconds
):After (using
$timing
):