Re: [whatwg/fetch] Add a render-blocking boolean flag to the request concept (PR #1432)

@xiaochengh commented on this pull request.

Thanks for reviewing!

> @@ -1869,6 +1869,12 @@ otherwise, it is unset.
 <a for=request>done flag</a>, and <a for=request>timing allow failed flag</a> are used as
 bookkeeping details by the <a for=/>fetch</a> algorithm.
 
+<p>A <a for=/>request</a> has an associated boolean
+<dfn export for=request id=concept-request-render-blocking>render-blocking</dfn>.

Done.

> @@ -3984,8 +3990,9 @@ the request.
 
  <li>
   <p>If <var>request</var>'s <a for=request>priority</a> is null, then use <var>request</var>'s
-  <a for=request>initiator</a> and <a for=request>destination</a> appropriately in setting
-  <var>request</var>'s <a for=request>priority</a> to a user-agent-defined object.
+  <a for=request>initiator</a>, <a for=request>destination</a> and

Done.

> +<p>A <a for=/>request</a> has an associated boolean
+<dfn export for=request id=concept-request-render-blocking>render-blocking</dfn>.
+Unless stated otherwise, it is false.
+
+<p class=note>This flag is for exclusive use by HTML's render-blocking mechanism. [[!HTML]]

Done.

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

Message ID: <whatwg/fetch/pull/1432/review/982341867@github.com>

Received on Monday, 23 May 2022 21:12:28 UTC