Re: [whatwg/fetch] Initial resource timing integration. (#1185)

> Outstanding issues:
> 
> * [ ]  start time isn't set
> * [ ]  if TAO isn't there we should reset to start time, not fetch start time

Not sure what you mean. when TAO isn't there we reset both fetch start time and start time, to avoid exposing the fact that there were redirects.

> * [ ]  I think we should rename fields to more accurately capture their semantics:
>   
>   * fetch start time -> final fetch start time (even that isn't super clear, but I'm hesitant to use final main fetch start time; one thing that is weird with final fetch start time is that with a 401 scenario it wouldn't capture the time the subsequent authenticated fetch started, as that doesn't go through main fetch)

Right, it would capture that start of that fetch, as 401 is not exactly a redirect.

>   * request start time -> network request start time (it's 0 if there's a service worker involved)
>   * response start time -> network response start time (it's 0 if there's a service worker involved)
>   * response end time -> end time (aligns with start time and is clearer if there's a service worker involved as it'll be non-0)

OK. I don't mind the renames

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1185#issuecomment-806479479