Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796)

@guohuideng2024 commented on this pull request.



> +         <li><p>Let <var>filteredCoding</var> be "<code>unknown</code>".
+
+         <li><p>If <var>codings</var> is null, then set <var>filteredCoding</var> to the empty string.
+
+         <li><p>Otherwise, if <var>codings</var>'s <a for=list>size</a> is 2 or more, then set
+         <var>filteredCoding</var> to "<code>multiple</code>".
+
+         <li><p>Otherwise, if <var>codings</var>[0] is the empty string, or it is supported by the user agent,
+         and is a <a>byte-case-insensitive</a> match for an entry listed in the
+         <a href="https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#content-coding">
+         <cite>HTTP Content Coding Registry</cite></a> of [[!IANA-HTTP-PARAMS]], then set
+         <var>filteredCoding</var> to <var>codings</var>[0].
+
+         <li><p>Set <var>response</var>'s <a for=response>body info</a>'s
+         <a for="response body info">content encoding</a> to the result of
+         <a lt=byte-lowercased>byte-lowercasing</a>  <var>filteredCoding</var>.

Done. This sentence is modified, and the superfluous space is gone

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

Message ID: <whatwg/fetch/pull/1796/review/2769021207@github.com>