Editorial: add <div algorithm> to HTTP extensions

Related to #1526.

Author: dlrobertson

fetch.bs

@@ -3214,6 +3214,7 @@ request <a for=/>header</a> indicates where a
 
 <hr>
 
+<div algorithm>
 <p>To <dfn id=append-a-request-origin-header>append a request `<code>Origin</code>` header</dfn>,
 given a <a for=/>request</a> <var>request</var>, run these steps:
 
@@ -3264,6 +3265,7 @@ given a <a for=/>request</a> <var>request</var>, run these steps:
 <p class=note>A <a for=/>request</a>'s <a for=request>referrer policy</a> is taken into account for
 all fetches where the fetcher did not explicitly opt into sharing their <a for=/>origin</a> with the
 server, e.g., via using the <a>CORS protocol</a>.
+</div>
 
 
 <h3 id=http-cors-protocol>CORS protocol</h3>
@@ -3657,6 +3659,7 @@ consideration for the security consequences. New exceptions can be proposed by
 <p>The `<code>Content-Length</code>` header is largely defined in HTTP. Its processing model is
 defined here as the model defined in HTTP is not compatible with web content. [[HTTP]]
 
+<div algorithm>
 <p>To <dfn export for="header list" lt="extract a length|extracting a length">extract a length</dfn>
 from a <a for=/>header list</a> <var>headers</var>, run these steps:
 
@@ -3684,13 +3687,15 @@ from a <a for=/>header list</a> <var>headers</var>, run these steps:
 
  <li><p>Return <var>candidateValue</var>, interpreted as decimal number.
 </ol>
+</div>
 
 
 <h3 id=content-type-header>`<code>Content-Type</code>` header</h3>
 
 <p>The `<code>Content-Type</code>` header is largely defined in HTTP. Its processing model is
 defined here as the model defined in HTTP is not compatible with web content. [[HTTP]]
 
+<div algorithm>
 <p>To
 <dfn export for="header list" lt="extract a MIME type|extracting a MIME type" id=concept-header-extract-mime-type>extract a MIME type</dfn>
 from a <a for=/>header list</a> <var>headers</var>, run these steps:
@@ -3743,6 +3748,7 @@ from a <a for=/>header list</a> <var>headers</var>, run these steps:
 
  <li><p>Return <var>mimeType</var>.
 </ol>
+</div>
 
 <p class=warning>When <a>extract a MIME type</a> returns failure or a <a for=/>MIME type</a> whose
 <a for="MIME type">essence</a> is incorrect for a given format, treat this as a fatal error.
@@ -3805,6 +3811,7 @@ Content-Type:
  </table>
 </div>
 
+<div algorithm>
 <p>To <dfn export>legacy extract an encoding</dfn> given failure or a <a for=/>MIME type</a>
 <var>mimeType</var> and an <a for=/>encoding</a> <var>fallbackEncoding</var>, run these steps:
 
@@ -3828,6 +3835,7 @@ Content-Type:
 
  <p>It is denoted as legacy as modern formats are to exclusively use <a for=/>UTF-8</a>.
 </div>
+</div>
 
 
 <h3 id=x-content-type-options-header>`<code>X-Content-Type-Options</code>` header</h3>
@@ -3838,6 +3846,7 @@ response <a for=/>header</a> can be used to require checking of a <a for=/>respo
 `<code>Content-Type</code>` <a for=/>header</a> against the <a for=request>destination</a> of a
 <a for=/>request</a>.
 
+<div algorithm>
 <p>To <dfn export>determine nosniff</dfn>, given a <a for=/>header list</a> <var>list</var>, run
 these steps:
 
@@ -3853,6 +3862,7 @@ these steps:
 
  <li><p>Return false.
 </ol>
+</div>
 
 <p>Web developers and conformance checkers must use the following <a for=header>value</a>
 <a>ABNF</a> for `<a http-header><code>X-Content-Type-Options</code></a>`:
@@ -3862,6 +3872,7 @@ X-Content-Type-Options           = "nosniff" ; case-insensitive
 </code></pre>
 
 
+<div algorithm="should response to request be blocked due to nosniff">
 <h4 lt="should response to request be blocked due to nosniff" dfn id=should-response-to-request-be-blocked-due-to-nosniff?>Should
 <var>response</var> to <var>request</var> be blocked due to nosniff?</h4>
 
@@ -3888,6 +3899,7 @@ X-Content-Type-Options           = "nosniff" ; case-insensitive
 <p class="note no-backref">Only <a for=/>request</a> <a for=request>destinations</a> that are
 <a for=request/destination>script-like</a> or "<code>style</code>" are considered as any exploits
 pertain to them. Also, considering "<code>image</code>" was not compatible with deployed content.
+</div>
 
 
 <h3 id=cross-origin-resource-policy-header>`<code>Cross-Origin-Resource-Policy</code>` header</h3>
@@ -3905,6 +3917,7 @@ response <a for=/>header</a> can be used to require checking a <a for=/>request<
 Cross-Origin-Resource-Policy     = %s"same-origin" / %s"same-site" / %s"cross-origin" ; case-sensitive
 </code></pre>
 
+<div algorithm>
 <p>To perform a <dfn export>cross-origin resource policy check</dfn>, given an <a for=url>origin</a>
 <var>origin</var>, an <a for=/>environment settings object</a> <var>settingsObject</var>, a string
 <var>destination</var>, a <a for=/>response</a> <var>response</var>, and an optional boolean
@@ -3946,7 +3959,9 @@ Cross-Origin-Resource-Policy     = %s"same-origin" / %s"same-site" / %s"cross-or
 <var>response</var> is either the <a for="filtered response">internal response</a> of an
 <a>opaque filtered response</a> or a <a for=/>response</a> which will be the
 <a for="filtered response">internal response</a> of an <a>opaque filtered response</a>. [[HTML]]
+</div>
 
+<div algorithm>
 <p>To perform a <dfn>cross-origin resource policy internal check</dfn>, given an
 <a for=url>origin</a> <var>origin</var>, an <a for=/>embedder policy value</a>
 <var>embedderPolicyValue</var>, a <a for=/>response</a> <var>response</var>, and a boolean
@@ -4029,7 +4044,9 @@ Cross-Origin-Resource-Policy     = %s"same-origin" / %s"same-site" / %s"cross-or
     match a securely-transported initiator.
   </dl>
 </ol>
+</div>
 
+<div algorithm>
 <p>To <dfn>queue a cross-origin embedder policy CORP violation report</dfn>, given a
 <a for=/>response</a> <var>response</var>, an <a for=/>environment settings object</a>
 <var>settingsObject</var>, a string <var>destination</var>, and a boolean <var>reportOnly</var>,
@@ -4083,6 +4100,7 @@ run these steps:
  <a for="environment settings object">global object</a> given the
  <a>"<code>coep</code>" report type</a>, <var>endpoint</var>, and <var>body</var>. [[!REPORTING]]
 </ol>
+</div>