Re: [whatwg/fetch] [draft] Pass in content type to resource-timing (PR #1481)

@abinpaul1 commented on this pull request.



> @@ -4383,6 +4383,13 @@ steps:
 
      <li><p>Let <var>bodyInfo</var> be <var>response</var>'s <a for=response>body info</a>.
 
+     <li><p>Let <var>mimeType</var> be the empty string if <var>fetchParams</var>'s
+     <a for="fetch params">request</a>'s <a for=request>mode</a> is "<code>navigate</code>" and
+     <var>response</var>'s <a for=response>URL</a>'s <a for=url>origin</a> is not
+     <a>same origin</a> with <var>request</var>'s <a for=request>origin</a>, and
+     result of <a for="header list">extracting a MIME type</a> from <var>response</var>'s

I've moved content-type inside `body info`. But can we rely on `body info`'s initialization for `content type` as well ? 

`body info` initialization seems to depend on [timing allow passed flag](https://fetch.spec.whatwg.org/#concept-response-timing-allow-passed). In [fetch response handover](https://fetch.spec.whatwg.org/#fetch-finale) 3.3.5, `body info` is reinitialized depending on `timing allow passed flag` which is different from the conditions we need for `content type`

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

Message ID: <whatwg/fetch/pull/1481/review/1103308599@github.com>