From 7358cbde582e87c59f36f43694f2cea7c7df0560 Mon Sep 17 00:00:00 2001
From: Ilya Grigorik <ilya@igvita.com>
Date: Mon, 15 Aug 2016 11:44:27 -0700
Subject: [PATCH] responseEnd is not subject to TAO

This was mistakenly introduced in a previous [1] refactoring of the
spec. For related discussion, see [2].

[1] https://github.com/w3c/resource-timing/commit/88bb58554c4fe792e5d4647544f5d2690498c5e1
[2] https://github.com/w3c/resource-timing/issues/64
---
 index.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 34ce7b3..47bdca9 100644
--- a/index.html
+++ b/index.html
@@ -563,11 +563,9 @@ <h3>The <code>PerformanceResourceTiming</code> Interface</h3>
 <ol class="algorithm">
 <li>
 The time immediately after the user agent receives the last byte of the response or immediately before the transport connection is closed, whichever comes first. The resource here can be received either from <a
-href="https://www.w3.org/TR/html5/browsers.html#relevant-application-cache">relevant application caches</a>, or from local resources or from the server if the last non-redirected <a href="https://www.w3.org/TR/html5/infrastructure.html#fetch">fetch</a> of the resource passes the <a>timing allow check</a> algorithm.
+href="https://www.w3.org/TR/html5/browsers.html#relevant-application-cache">relevant application caches</a>, local resources, or from the server.
 </li>
-<li>zero, otherwise.</li>
 </ol>
-
 <p dfn-for='PerformanceResourceTiming'>
 On getting, the <dfn>transferSize</dfn> attribute MUST return as follows:
 </p>