64
64
subjectPrefix : "[ResourceTiming]" ,
65
65
github : "https://github.com/w3c/resource-timing/" ,
66
66
caniuse : "resource-timing" ,
67
- xref : [ "html" , "hr-time-3" , "performance-timeline-2" , "fetch" , "infra" ] ,
67
+ xref : {
68
+ specs : [ "hr-time-3" , "performance-timeline-2" , "xhr" ] ,
69
+ profile : "web-platform" ,
70
+ }
68
71
} ;
69
72
</ script >
70
73
</ head >
212
215
< p >
213
216
The term < dfn > DOM</ dfn > is used to refer to the API set made available
214
217
to scripts in Web applications, and does not necessarily imply the
215
- existence of an actual < a data-cite =" DOM#document " > Document</ a > object
216
- or of any other < a data-cite =" DOM#node " > Node</ a > objects as defined in
218
+ existence of an actual [= Document=] </ a > object
219
+ or of any other [= Node=] </ a > objects as defined in
217
220
the [[DOM]] specification.
218
221
</ p >
219
222
< p >
235
238
svg.
236
239
</ p >
237
240
< p >
238
- The term < dfn > cross-origin</ dfn > is used to mean non < a data-cite =
239
- "HTML#same-origin "> same origin</ a > .
241
+ The term < dfn > cross-origin</ dfn > is used to mean non [=same origin=]</ a > .
240
242
</ p >
241
243
< p >
242
244
The term < dfn > current document</ dfn > refers to the document associated
@@ -271,20 +273,14 @@ <h2>
271
273
< h3 >
272
274
Introduction
273
275
</ h3 >
274
- < p >
276
+ < p data-fn-for =" html " >
275
277
The < a > PerformanceResourceTiming</ a > interface facilitates timing
276
278
measurement of downloadable resources. For example, this interface is
277
- available for < a data-cite =
278
- "XHR#interface-xmlhttprequest "> XMLHttpRequest</ a > objects [[XHR]],
279
- HTML elements [[HTML]] such as < a data-cite =
280
- "HTML#the-iframe-element "> iframe</ a > , < a data-cite =
281
- "HTML#the-img-element "> img</ a > , < a data-cite =
282
- "HTML#the-script-element "> script</ a > , < a data-cite =
283
- "HTML#the-object-element "> object</ a > , < a data-cite =
284
- "HTML#the-embed-element "> embed</ a > , and < a data-cite =
285
- "HTML#the-link-element "> link</ a > with the link type of < a data-cite =
286
- "HTML#link-type-stylesheet "> stylesheet</ a > , and SVG elements
287
- [[SVG11]] such as < a data-cite =
279
+ available for {{XMLHttpRequest}} objects [[XHR]],
280
+ HTML elements [[HTML]] such as [^iframe^], [^img^],
281
+ [^script^], [^object^], [^embed^]
282
+ and [^link^] with the link type of [^link/rel/stylesheet^],
283
+ and SVG elements [[SVG11]] such as < a data-cite =
288
284
"SVG11/struct.html#SVGElement "> svg</ a > .
289
285
</ p >
290
286
</ section >
@@ -293,12 +289,11 @@ <h3>
293
289
Resources Included in the < a > PerformanceResourceTiming</ a > Interface
294
290
</ h3 >
295
291
< p >
296
- All resource < dfn data-cite =" Fetch#concept-request " > Request</ dfn > s
297
- < a data-cite =" FETCH#concept- fetch" > fetched </ a > by a non-null
298
- < dfn data-cite =" Fetch#concept- request-client " > client </ dfn > MUST be
292
+ All resource [= Request=] s
293
+ [= fetch=]ed </ a > by a non-null
294
+ [= request/client=] MUST be
299
295
included as < a > PerformanceResourceTiming</ a > objects in the
300
- < a > client</ a > 's < dfn data-cite =
301
- "HTML#concept-settings-object-global "> global object</ dfn > 's
296
+ [=request/client=]'s [=environment settings object/global object=]'s
302
297
< a data-cite =
303
298
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
304
299
Timeline</ a > , unless excluded from the timeline as part of the
308
303
< a > PerformanceResourceTiming</ a > objects in the < a data-cite =
309
304
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
310
305
Timeline</ a > [[PERFORMANCE-TIMELINE-2]]. Resources for which the
311
- < a data-cite =" FETCH#concept- fetch" > fetch </ a > was initiated, but was
306
+ [= fetch=] was initiated, but was
312
307
later aborted (e.g. due to a network error) MAY be included as
313
308
< a > PerformanceResourceTiming</ a > objects in the < a data-cite =
314
309
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
@@ -331,15 +326,15 @@ <h3>
331
326
Timeline</ a > . The user agent might not re-request the URL for the
332
327
second HTML < code > IMG</ code > element, instead using the existing
333
328
download it initiated for the first HTML < code > IMG</ code > element. In
334
- this case, the < a data-cite =" FETCH#concept- fetch" > fetch </ a > of the
329
+ this case, the [= fetch=] of the
335
330
resource by the first < code > IMG</ code > element would be the only
336
331
occurrence in the < a data-cite =
337
332
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
338
333
Timeline</ a > .
339
334
</ li >
340
335
< li > If the < code > src</ code > attribute of a HTML < code > IMG</ code >
341
336
element is changed via script, both the [=fetch=] of the original
342
- resource as well as the < a data-cite =" FETCH#concept- fetch" > fetch </ a >
337
+ resource as well as the [= fetch=] </ a >
343
338
of the new URL would be included as < a > PerformanceResourceTiming</ a >
344
339
objects in the < a data-cite =
345
340
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
@@ -350,15 +345,15 @@ <h3>
350
345
load the < code > about:blank</ code > document for the
351
346
< code > IFRAME</ code > . If at a later time the < code > src</ code >
352
347
attribute is changed dynamically via script, the user agent may
353
- < a data-cite =" FETCH#concept- fetch" > fetch </ a > the new URL resource for
348
+ [= fetch=] the new URL resource for
354
349
the < code > IFRAME</ code > . In this case, only the [=fetch=] of the new
355
350
URL would be included as a < a > PerformanceResourceTiming</ a > object in
356
351
the < a data-cite =
357
352
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
358
353
Timeline</ a > .
359
354
</ li >
360
355
< li > If an < code > XMLHttpRequest</ code > is generated twice for the same
361
- canonical URL, both < a data-cite =" FETCH#concept-fetch " > fetches</ a > of
356
+ canonical URL, both [= fetches=] </ a > of
362
357
the resource would be included as a < a > PerformanceResourceTiming</ a >
363
358
object in the < a data-cite =
364
359
"PERFORMANCE-TIMELINE-2#performance-timeline "> Performance
664
659
</ ol >
665
660
< p class ='note '>
666
661
A user agent implementing < a > PerformanceResourceTiming</ a > would need
667
- to include < code > "resource"</ code > in < a data-cite =
668
- "PERFORMANCE-TIMELINE-2#supportedentrytypes-attribute "> supportedEntryTypes</ a > .
662
+ to include < code > "resource"</ code > in {{PerformanceObserver/supportedEntryTypes}}.
669
663
This allows developers to detect support for Resource Timing.
670
664
</ p >
671
665
</ section >
845
839
timing secondary buffer current size</ a > .
846
840
</ li >
847
841
< li > If < a > can add resource timing entry</ a > returns false, then
848
- < a data-cite ="DOM/#concept-event-fire "> fire an event</ a > named
849
- < code > resourcetimingbufferfull</ code > at the < a data-cite =
850
- "HR-TIME-2/#idl-def-performance "> Performance</ a > object.
842
+ [=fire an event=]</ a > named
843
+ < code > resourcetimingbufferfull</ code > at the {{Performance}} object.
851
844
</ li >
852
845
< li > Run < a > copy secondary buffer</ a > .
853
846
</ li >
0 commit comments