WIP: Report resource timing for most HTML elements1 #7147
Conversation
Create a reusable function that fetches a resource and reports the timing when done, given an initiator type. Implement for the following fetches: - link (not including style, yet) - script (classic, module, worker, worklet, import) - img (src, srcset) - link (type=image) - Media (audio, video, track, poster) - A (download, ping) TBD: - Loading resources from CSS (mostly not in the HTML spec) - preload/prefetch/prerender - frames/iframes (might not be needed, as it's a navigation) See whatwg#6542
|
@domenic, available for an r? |
noamr
changed the title
| @@ -31879,6 +31905,9 @@ interface <dfn interface>HTMLObjectElement</dfn> : <span>HTMLElement</span> { | |||
| <li> | |||
| <!--FETCH--><p><span data-x="concept-fetch">Fetch</span> <var>request</var>.</p> | |||
|
|
|||
| <p class="note"><code>object</code> and <code>embed</code> elements do not report their | |||
| resource timing.</p> | |||
There was a problem hiding this comment.
I don't think this is true in most implementations. (at least for embed
There was a problem hiding this comment.
It was specified in the Resource Timing spec.
There was a problem hiding this comment.
Oops, it wasn't. I don't remember where I got this from.
| <p><i>Fetch the image</i>: <span data-x="concept-fetch">Fetch</span> <var>request</var>. Let | ||
| this instance of the <span data-x="concept-fetch">fetching</span> algorithm be associated with | ||
| <var>image request</var>. | ||
| <p><i>Fetch the image</i>: <span data-x="fetch a resource">Fetch</span> <var>request</var> with |
There was a problem hiding this comment.
I think it'd be better to indicate in the text that this is calling "fetch a resource" and not "Fetch" (here and elsewhere)
Thanks, though actually I might have to revamp. Using |
|
Doing this more gradually, see #7180 |
Report resource timing for several resources.
Create a reusable function that fetches a resource and reports the
timing when done, given an initiator type.
Implement for the following fetches:
TBD:
See #6542
At least two implementers are interested (and none opposed):
This is already implemented in Chrome, Safari and Firefox, and was previously spec'ed as part of resource timing.
Some of the specific discrepancies will be handled as part of WPT.
Tests are written as part of the resource timing tests. TBD: several detailed test for uncovered specifics.
Implementation bugs are filed:
(See WHATWG Working Mode: Changes for more details.)
/iframe-embed-object.html ( diff )
/images.html ( diff )
/infrastructure.html ( diff )
/input.html ( diff )
/links.html ( diff )
/media.html ( diff )
/semantics.html ( diff )
/urls-and-fetching.html ( diff )
/webappapis.html ( diff )
/workers.html ( diff )