- From: Noam Rosenthal <notifications@github.com>
- Date: Wed, 27 Jul 2022 07:06:44 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 27 July 2022 14:06:57 UTC
@noamr commented on this pull request. > @@ -301,6 +301,9 @@ following <a for=struct>items</a>: [[RESOURCE-TIMING]] [[NAVIGATION-TIMING]] <dt><dfn export for="response body info" id="fetch-timing-info-decoded-body-size">decoded size</dfn> (default 0) <dd>A number. + <dt><dfn export for="response body info" id="fetch-timing-info-response-status">response This is not needed. You have [response's status](https://fetch.spec.whatwg.org/#concept-response-status) when you set the `report timing steps` in [fetch response handover](https://fetch.spec.whatwg.org/#fetch-finale). I would add it as another parameter to `Mark resource timing`. Also, as we talked on the Chromium CL, I don't think we should automatically make this TAO-protected rather than CORS-protected. It's not exactly timing information. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/1468#pullrequestreview-1052573304 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/pull/1468/review/1052573304@github.com>
Received on Wednesday, 27 July 2022 14:06:57 UTC