Skip to content

Commit 27526ba

Browse files
committed
recommendation for when add/queue steps should run
Closes #55.
1 parent 603d1bd commit 27526ba

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

index.html

+8-1
Original file line numberDiff line numberDiff line change
@@ -855,9 +855,16 @@ <h3>Processing Model</h3>
855855
</li>
856856
<li><a href='https://www.w3.org/TR/performance-timeline-2/#dfn-queue-a-performanceentry'>Queue</a> the <a>PerformanceResourceTiming</a> object.
857857
</li>
858-
<li><a data-lt='add a PerformanceResourceTiming entry'>Add</a> the <a>PerformanceResourceTiming</a> object.
858+
<li><a data-lt='add a PerformanceResourceTiming entry'>Add</a> the <a>PerformanceResourceTiming</a> object to the <a href='https://www.w3.org/TR/performance-timeline-2/#dfn-performance-entry-buffer'>performance entry buffer</a>.</li>
859859
</li>
860860
</ol>
861+
<p class="note">
862+
This specification does not specify whether steps 20 and 21 should run
863+
before or after the <code>load</code> event of the resource. However, where
864+
applicable, the user agent is encouraged to run them after the
865+
<code>load</code> event of the resource has finished—see
866+
<a href="https://github.com/w3c/resource-timing/issues/55#issuecomment-260075811">related discussion</a>.
867+
</p>
861868
</section>
862869
<section id="monotonic-clock">
863870
<h3>Monotonic Clock</h3>

0 commit comments

Comments
 (0)