1811291 - Addition of interim response timings for Resource Timing

Status: NEW

(Core :: DOM: Networking, enhancement, P2)

Description

[Benjamin De Kosnik [:bdekoz]]

Steps to reproduce:

HTTP interim response status code in Resource Timing

Resource Timing PR : https://github.com/w3c/resource-timing/pull/366
Fetch PR : https://github.com/whatwg/fetch/pull/1483

Explainer : https://github.com/abinpaul1/resource-timing/blob/explainer-resource-response-status/Explainers/Response_Status_Code.md

Request for position mozilla : https://github.com/mozilla/standards-positions/issues/722

Comment 2

[Dave Hunt [:davehunt] [he/him] ⌚BST]

https://github.com/w3c/resource-timing/issues/345#issuecomment-2377911822 is proposing to remove firstInterimResponseStart and add finalResponseHeadersStart. Do we have a position on this?

Comment 3

[Valentin Gosu [:valentin] (he/him)]

(In reply to Dave Hunt [:davehunt] [he/him] ⌚BST from comment #2)

https://github.com/w3c/resource-timing/issues/345#issuecomment-2377911822 is proposing to remove firstInterimResponseStart and add finalResponseHeadersStart. Do we have a position on this?

I think this is a good change, and worth implementing ASAP.

Comment 4

[Barry Pollard]

Just to be clear what we landed on in the end was NOT removing firstInterimResponseStart but adding finalResponseHeadersStart in addition. As well as making reponseStart the first non-zero timing of those two:
https://github.com/w3c/resource-timing/issues/345#issuecomment-2450475244

Mozilla position from Sean Feng is positive:
https://github.com/mozilla/standards-positions/issues/1108