Re: [whatwg/fetch] Call `finalize and report timing` automatically on end-of-body (PR #1413)

@noamr commented on this pull request.



> @@ -1404,6 +1420,30 @@ this flag set are subject to additional processing requirements.
 <p>A <a for=/>request</a> has an associated <dfn for=request export>service-workers mode</dfn>, that
 is "<code>all</code>" or "<code>none</code>". Unless stated otherwise it is "<code>all</code>".
 
+<p>A <a for=/>request</a> has an associated
+<dfn for=request export>initiator type</dfn>, which is null,
+"<code>audio</code>",
+"<code>beacon</code>",
+"<code>body</code>",
+"<code>css</code>",
+"<code>early-hint</code>",

Yes, that's the idea of `initiatorType`. You want to know where the request came from, not which kind of request it is (which `destination` already covers). That's why e.g. a CSS image request would have a destination `image` and an initiator `css`.

 I do agree that `initiatorType` is a bit inconsistent, and there are several open issues like https://github.com/w3c/resource-timing/issues/132 to address this. But I want the spec to catch up with implementations before we get to it.

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

Message ID: <whatwg/fetch/pull/1413/review/1005514469@github.com>