Skip to content

Commit 76f47d3

Browse files
authored
Fix when a script element is implicitly potentially render-blocking
Fixes #7893, which is a bug introduced by #7857.
1 parent 2f901a7 commit 76f47d3

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

source

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60126,7 +60126,9 @@ o............A....e
6012660126

6012760127
<p>A <code>script</code> element is <span>implicitly potentially render-blocking</span> if the
6012860128
element's <span data-x="concept-script-type">script's type</span> is set and is equal to
60129-
"<code data-x="">classic</code>", and the element is <span>"parser-inserted"</span>.</p>
60129+
"<code data-x="">classic</code>", the element is <span>"parser-inserted"</span>, and the
60130+
element does not have an <code data-x="attr-script-async">async</code> or
60131+
<code data-x="attr-script-defer">defer</code> attribute.</p>
6013060132

6013160133
<hr>
6013260134

0 commit comments

Comments
 (0)