Navigation Timing: performance.timing.requestStart before performance.timing.navigationStart
Reported by
nn1436...@gmail.com,
Mar 28 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: Copied from original issue as it is requested to open a new issue. https://bugs.chromium.org/p/chromium/issues/detail?id=127644 1. Open Chrome and open the dev tools (F12) 2. Add a watch expression for "performance.timing.requestStart - performance.timing.navigationStart;" 3. Enter the URL www.google.com to go to google 4. Once the page has loaded enter the URL www.yahoo.com to go to yahoo 5. Once the page has loaded, navigate quickly forward and back a few times. 6. Observe the watch expression take a negative value Happens on fast double redirection too. What is the expected behavior? According to the W3C navigation timing api spec, navigationStart should take place before request start and not after. What went wrong? navigationStart through to connectEnd all take the same value X. requestStart has value Y and Y < X. From request start onwards the marks have normal increasing values. Did this work before? No Chrome version: 56 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0 Seems like issue always existed and has never been fixed.
,
Apr 4 2017
,
Apr 6 2017
Thanks for filing the issue. Unable to reproduce the issue on windows 10 as per the steps mentioned in comment#0 on chrome reported version-M56 , stable-57.0.2987.133 & Canary-59.0.3063.4. Unable to find a negative value in dev tools. Please find the attached screencast for reference & let us know if we miss any steps to reproduce the issue. Please check the issue on latest chrome stable/Canary versions & if still issue persists, it would be more helpful if you can provide us the clear screencast of the exact issue for better triaging.
,
Apr 9 2017
I tried with Chrome 57. Couldn't reproduce from the first try. I'll check whether it happens again.
,
Apr 9 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2017
As per comment#5 changing the status as Wontfix. nn1436401@ please feel free to file a new bug if you face the issue again. Thanks.. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ksakamoto@chromium.org
, Mar 28 2017