Re: [whatwg/fetch] Add more timing information about (interim) responses (PR #1483)

> Thanks for pushing this @noamr! One nit and tests remain and a bit of process feedback for next time.
> 
> I find it rather odd that the scope of this PR has been reduced based on what Chromium deemed worthy to implement right now. Especially without signals from other stakeholders that that seems reasonable. But perhaps this was discussed somewhere?

It wasn't discussed, it's perhaps my misunderstanding of how the process should look like.
Right now it seems like other vendors are supportive of the whole thing, but no vendor is actively implementing anything but `firstInterimResponseStart`. This includes WPT coverage. Given that, I thought it would be the right thing to first merge `firstInterimResponseStart` and then merge the other ones when there is a first implementer that's also going to spend the time on authoring WPTs for `responseHeadersEnd` and `responseBodyStart`.

> 
> Either way, given the relatively small scope of this feature I'm okay with it, but OP will need updating.
> 
> As for tests:
> 
> * Next time please land them as `.tentative` until specifications PRs land/are about to land.

Will do

> * Please add some tests where a non-103 1xx comes first. E.g., 1) 110 103 200, 2) 199 200.

On it

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

Message ID: <whatwg/fetch/pull/1483/c1537296345@github.com>