From 76f47d33433260e143c9aedbba4cd27b6a78b57c Mon Sep 17 00:00:00 2001
From: Xiaocheng Hu <xiaochengh@chromium.org>
Date: Mon, 16 May 2022 21:06:08 +0000
Subject: [PATCH] Fix when a `script` element is implicitly potentially
 render-blocking

Fixes #7893, which is a bug introduced by #7857.
---
 source | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/source b/source
index 81cbb67d3b0..00d43aaa88d 100644
--- a/source
+++ b/source
@@ -60126,7 +60126,9 @@ o............A....e
 
   <p>A <code>script</code> element is <span>implicitly potentially render-blocking</span> if the
   element's <span data-x="concept-script-type">script's type</span> is set and is equal to
-  "<code data-x="">classic</code>", and the element is <span>"parser-inserted"</span>.</p>
+  "<code data-x="">classic</code>", the element is <span>"parser-inserted"</span>, and the
+  element does not have an <code data-x="attr-script-async">async</code> or
+  <code data-x="attr-script-defer">defer</code> attribute.</p>
 
   <hr>