Report <a> ping, <a> download, and script loading to Resource Timing

Author: noamr

source

@@ -2492,6 +2492,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
      <li><dfn data-x="serialize-a-response-url-for-reporting" data-x-href="https://fetch.spec.whatwg.org/#serialize-a-response-url-for-reporting">serialize a response URL for reporting</dfn></li>
      <li><dfn data-x="body safely extract" data-x-href="https://fetch.spec.whatwg.org/#bodyinit-safely-extract">safely extracting a body</dfn></li>
      <li><dfn data-x-href="https://fetch.spec.whatwg.org/#process-response-end-of-body">processResponseConsumeBody</dfn></li>
+     <li><dfn data-x-href="https://fetch.spec.whatwg.org/#fetch-processresponseendofbody">processResponseEndOfBody</dfn></li>
      <li>
       <dfn data-x="concept-response"
       data-x-href="https://fetch.spec.whatwg.org/#concept-response">response</dfn> and its
@@ -24202,12 +24203,14 @@ document.body.appendChild(wbr);</code></pre>
    <li><p>Optionally, return. (For example, the user agent might wish to ignore any or
    all ping URLs in accordance with the user's expressed preferences.)</p></li>
 
+   <li><p>Let <var>settingsObject</var> be the element's <span>node document</span>'s
+   <span>relevant settings object</span>.</p></li>
+
    <li><p>Let <var>request</var> be a new <span data-x="concept-request">request</span> whose
    <span data-x="concept-request-url">URL</span> is <var>ping URL</var>, <span
    data-x="concept-request-method">method</span> is `<code data-x="">POST</code>`, <span
    data-x="concept-request-body">body</span> is `<code data-x="">PING</code>`, <span
-   data-x="concept-request-client">client</span> is the <span>environment settings object</span> of
-   the <code>Document</code> containing the <span>hyperlink</span>, <span
+   data-x="concept-request-client">client</span> is <var>settingsObject</var>, <span
    data-x="concept-request-destination">destination</span> is the empty string,
    <span data-x="concept-request-credentials-mode">credentials mode</span> is "<code
    data-x="">include</code>", <span data-x="concept-request-referrer">referrer</span> is "<code
@@ -24239,7 +24242,12 @@ document.body.appendChild(wbr);</code></pre>
     </dl>
    </li>
 
-   <!--FETCH--><li><p><span data-x="concept-fetch">Fetch</span> <var>request</var>.</p></li>
+   <li><p><span data-x="concept-fetch">Fetch</span> <var>request</var>, with <i
+   data-x="processResponseEndOfBody">processResponseEndOfBody</i> given <span
+   data-x="concept-response">response</span> <var>res</var> set to <span>finalize and report
+   timing</span> with <var>res</var>, <var>settingsObject</var>'s <span
+   data-x="concept-settings-object-global">global object</span>, and "<code
+   data-x="">ping</code>".</p></li>
   </ol>
 
   <p>This may be done <span>in parallel</span> with the primary fetch, and is independent of the
@@ -91856,13 +91864,18 @@ document.querySelector("button").addEventListener("click", bound);
     remaining steps.</p>
 
     <p>Otherwise, <span data-x="concept-fetch">fetch</span> <var>request</var>. Return from this
-    algorithm, and run the remaining steps as part of the fetch's <span>process response</span> for
-    the <span data-x="concept-response">response</span> <var>response</var>.</p>
+    algorithm, and run the remaining steps as part of the fetch's <i
+    data-x="processResponseConsumeBody">processResponseConsumeBody</i> given <span
+    data-x="concept-response">response</span> <var>response</var>.</p>
 
     <p class="note"><var>response</var> can be either <span>CORS-same-origin</span> or
     <span>CORS-cross-origin</span>. This only affects how error reporting happens.</p>
    </li>
 
+   <li><p><span>Finalize and report timing</span> with <var>response</var>, <var>settings
+   object</var>'s <span data-x="concept-settings-object-global">global object</span>, and "<code
+   data-x="">script</code>".</p></li>
+
    <li><p>Set <var>response</var> to <var>response</var>'s <span>unsafe response</span>.</p></li>
 
    <li>
@@ -91925,10 +91938,15 @@ document.querySelector("button").addEventListener("click", bound);
     remaining steps.</p>
 
     <p>Otherwise, <span data-x="concept-fetch">fetch</span> <var>request</var>. Return from this
-    algorithm, and run the remaining steps as part of the fetch's <span>process response</span> for
-    the <span data-x="concept-response">response</span> <var>response</var>.</p>
+    algorithm, and run the remaining steps as part of the fetch's <i
+    data-x="processResponseConsumeBody">processResponseConsumeBody</i> given <span
+    data-x="concept-response">response</span> <var>response</var>.<p>
    </li>
 
+   <li><p><span>Finalize and report timing</span> with <var>response</var>, <var>fetch client
+   settings object</var>'s <span data-x="concept-settings-object-global">global object</span>, and
+   "<code data-x="">other</code>".</p></li>
+
    <li><p>Set <var>response</var> to <var>response</var>'s <span>unsafe response</span>.</p></li>
 
    <li>
@@ -91944,7 +91962,6 @@ document.querySelector("button").addEventListener("click", bound);
 
     <p>then asynchronously complete this algorithm with null, and return.</p>
    </li>
-
    <li>
     <p>If both of the following conditions are met:</p>
 
@@ -92002,6 +92019,10 @@ document.querySelector("button").addEventListener("click", bound);
     also finish their work synchronously.</p>
    </li>
 
+   <li><p><span>Finalize and report timing</span> with <var>response</var>, <var>settings
+   object</var>'s <span data-x="concept-settings-object-global">global object</span>, and "<code
+   data-x="">other</code>".</p></li>
+
    <li><p>Set <var>response</var> to <var>response</var>'s <span>unsafe response</span>.</p></li>
 
    <li>
@@ -92196,8 +92217,9 @@ document.querySelector("button").addEventListener("click", bound);
    "<code data-x="">fetching</code>".</p></li>
 
    <li>
-    <p><span data-x="concept-fetch">Fetch</span> <var>request</var>. To <span>process
-    response</span> for the <span data-x="concept-response">response</span> <var>response</var>:</p>
+    <p><span data-x="concept-fetch">Fetch</span> <var>request</var>, with <i
+    data-x="processResponseConsumeBody">processResponseConsumeBody</i> set to the following steps
+    given <span data-x="concept-response">response</span> <var>response</var>:</p>
 
     <ol>
      <li><p>Set <var>moduleResponsesMap</var>[<var>requestURL</var>] to
@@ -92602,12 +92624,17 @@ document.querySelector("button").addEventListener("click", bound);
     data-x="concept-response">response</span> <var>response</var>, run the remaining steps.</p>
 
     <p>Otherwise, <span data-x="concept-fetch">fetch</span> <var>request</var>. Return from this
-    algorithm, and run the remaining steps as part of the fetch's <span>process response</span> for
-    the <span data-x="concept-response">response</span> <var>response</var>.</p>
+    algorithm, and run the remaining steps as part of the fetch's <i
+    data-x="processResponseConsumeBody">processResponseConsumeBody</i> given <span
+    data-x="concept-response">response</span> <var>response</var>.</p>
 
     <p class="note"><var>response</var> is always <span>CORS-same-origin</span>.</p>
    </li>
 
+   <li><p><span>Finalize and report timing</span> with <var>response</var>, <var>fetch client
+   settings object</var>'s <span data-x="concept-settings-object-global">global object</span>, and
+   "<code data-x="">other</code>".</p></li>
+
    <li>
     <p>If either of the following conditions are met:</p>