Timing breakdown when using server push
Reported by
alicechi...@gmail.com,
Jul 5
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Analysis the network waterfall of a website using server push (eg. https://http2-push.io/) 2. Check the timing breakdown of a resource that is pushed by the server 3. Hover on the timing and check the breakdown. What is the expected behavior? The time on the bottom right corner should be the sum of the breakdown time. (as it is for non-server-pushed resources) What went wrong? The sum is larger than the sum of all timing listed. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: OS X 10.13.0 Flash Version:
,
Jul 5
Issue 860423 has been merged into this issue.
,
Jul 6
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 67.0.3396.99 using Mac 10.13.1 with the below mentioned steps. 1. Launched chrome 2. Navigated to https://http2-push.io/ 3. Inspected the page to open DevTools-> Network tab 4. Refreshed the page-> Clicked on http2-push.io/ Observed the summation of the time registered at the bottom right corner is correct. Attaching the screenshot the same. @Reporter: Could you please have a look at the screen shot and let us know if we have missed anything in the process. Any further inputs from your end may help us.
,
Jul 6
This issue is only for the resources that are using HTTP/2 server push. If you take a look at the timing breakdown of a pushed resource (eg. style.css or http2-push.js), is the summation still correct?
,
Jul 6
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 9
,
Dec 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Jul 5