Make <body> not optional if first child is noscript

tashasyarifah · zcorpan · web-flow · commit 6a77e6de72c5 · 2022-09-15T19:15:23.000+02:00
The `noscript` element is allowed in `head` and therefore it will be inserted to the `head` element by the parser if the `<body>` tag is omitted and `<noscript>` is the first non-whitespace token after `</head>`. This changes the syntax requirements so that it's not allowed to omit the `<body>` tag in this case. Fixes #7737 Co-authored-by: Simon Pieters <zcorpan@gmail.com>
diff --git a/source b/source
@@ -106808,10 +106808,10 @@ dictionary <dfn dictionary>StorageEventInit</dfn> : <span>EventInit</span> {
   <p>A <code>body</code> element's <span data-x="syntax-start-tag">start tag</span> may be omitted
   if the element is empty, or if the first thing inside the <code>body</code> element is not
   <span>ASCII whitespace</span> or a <span data-x="syntax-comments">comment</span>, except if the
-  first thing inside the <code>body</code> element is a <code>meta</code>, <code>link</code>,
-  <code>script</code>, <code>style</code>, or <code>template</code> element. <!-- Note that even if
-  the </head> end tag is present, the parser makes <style> and <script> elements between </head> and
-  <body> end up in the <head> instead of implying the <body> --></p>
+  first thing inside the <code>body</code> element is a <code>meta</code>, <code>noscript</code>,
+  <code>link</code>, <code>script</code>, <code>style</code>, or <code>template</code> element.
+  <!-- Note that even if the </head> end tag is present, the parser makes <style> and <script>
+  elements between </head> and <body> end up in the <head> instead of implying the <body> --></p>
 
   <!-- </body> -->
   <p>A <code>body</code> element's <span data-x="syntax-end-tag">end tag</span> may be omitted if the
