Network request timing view doesn't show service worker info |
|
Issue descriptionWhat steps will reproduce the problem? (1) Visit a webpage with a service worker which intercepts fetch events (2) Open DevTools network panel (3) Reload the page What is the expected result? The initial request should say that it was intercepted by the service worker in the timing information What happens instead? The initial request (which has less timing information) for the page doesn't say that it was waiting for the service worker in the timing information, whereas other requests say that they were
,
Nov 28
wanderview@ I don't think so, I'm pretty sure this is just a frontend issue here: https://cs.chromium.org/chromium/src/third_party/blink/renderer/devtools/front_end/network/RequestTimingView.js?l=126&rcl=9f875a248b4ed12cbfb0da9ec2872f3db1f87960 because the !timing case doesn't check to see if the request came from a service worker like this one: https://cs.chromium.org/chromium/src/third_party/blink/renderer/devtools/front_end/network/RequestTimingView.js?l=152&rcl=9f875a248b4ed12cbfb0da9ec2872f3db1f87960 I would be interested in doing a sanity check with navigation preload though. Would I expect that the initial response of a webpage with navigation preload does or does not come from a service worker?
,
Nov 29
navigation preload works like this: - The navigation to URL |x| begins - Browser sends a network request for |x| - Browser dispatches a FetchEvent for |x| to the service worker for URL x, and gives it the network response from the previous step - The service worker will typically respond to the request with that response, but may do any arbitrary thing. |
|
►
Sign in to add a comment |
|
Comment 1 by wanderview@chromium.org
, Nov 27