revisions

Author: bvandersloot-mozilla

fetch.bs

@@ -1958,7 +1958,7 @@ not always relevant and might require different behavior.
 "<code>client</code>".
 
 <p>A <a for=/>request</a> has an associated
-<dfn export for=request id=concept-request-navigation-initiator-origin>top-level navigation initiator origin</dfn>,
+<dfn export for=request>top-level navigation initiator origin</dfn>,
 which is an <a for=/>origin</a> or null. Unless stated otherwise it is null.
 
 <p class=note>"<code>client</code>" is changed to an <a for=/>origin</a> during
@@ -2249,7 +2249,7 @@ or "<code>object</code>".
 <hr>
 
 <div algorithm>
-<p>To compute the <dfn for=request id=concept-request-redirect-taint>redirect-taint</dfn> of a
+<p>To compute the <dfn for=request id=concept-request-tainted-origin>redirect-taint</dfn> of a
 <a for=/>request</a> <var>request</var>, perform the following steps. They return
 "<code>same-origin</code>", "<code>same-site</code>", or "<code>cross-site</code>".
 
@@ -4263,11 +4263,11 @@ prefetch, or to treat it differently when counting page visits.
 
 <h3 id=cookie-header>`<code>Cookie</code>` header</h3>
 
-<p>The `<code>Cookie</code>` header is largely defined in its own specification. [[COOKIES]].
-We define infrastructure to be able to use them conveniently here.
+<p>The `<code>Cookie</code>` header is largely defined in its own specification. We define
+additional infrastructure to be able to use them conveniently here. [[COOKIES]].
 
 <div algorithm>
-<p>To <dfn id=append-a-request-cookie-header>append a request `<code>Cookie</code>` header</dfn>,
+<p>To <dfn>append a request `<code>Cookie</code>` header</dfn>,
 given a <a for=/>request</a> <var>request</var>:
 
 <ol>
@@ -4305,7 +4305,7 @@ given a <a for=/>request</a> <var>request</var>:
 
 <div algorithm>
 <p>To
-<dfn id=parse-and-store-response-cookie-headers>parse and store response `<code>Set-Cookie</code>` headers</dfn>,
+<dfn>parse and store response `<code>Set-Cookie</code>` headers</dfn>,
 given a <a for=/>request</a> <var>request</var> and a <a for=/>response</a> <var>response</var>:
 
 <ol>
@@ -4316,7 +4316,7 @@ given a <a for=/>request</a> <var>request</var> and a <a for=/>response</a> <var
 
  <li><p>Let |isSecure| be false.
 
- <li><p>If <var>request</var>'s <a for=request>url</a>'s <a for=url>scheme</a> is
+ <li><p>If <var>request</var>'s <a for=request>current URL</a>'s <a for=url>scheme</a> is
  "<code>https</code>", then set |isSecure| to true.
 
  <li>
@@ -4376,17 +4376,7 @@ other specifications.
 </ol>
 </div>
 
-<div algorithm>
-<p> To <dfn export>clear site cookies</dfn> for <a for=/>origin</a> <var>origin</var>, run these steps:
-
-<ol>
- <li><p>Remove all cookies that were stored with a host is either equal to |origin|'s <a for=url>host</a>,
- or have a <a>registrable domain</a> equal to |origin|'s <a for=url>host</a>'s <a>registrable domain</a>.
 
- <p class=XXX>The cookie specification doesn't yet have a way to do this algorithmically, so we
- settle for this definition.
-</ol>
-</div>
 
 <h2 id=fetching>Fetching</h2>