[Resource Timings] Requirements and use-cases

Here's a capture of the requirements and use cases we've been discussing over the past few weeks. Feel free to reply to add more.

Resource Timing Goals

1.       Ease of use and access to the resource timings - the interface's usage pattern should align closely with Navigation Timing, producing predictable results.

2.       Security-information about what the end-user had been doing on a previous page navigation and the location of past navigations must not be disclosed.

3.       Performs well in user agents - User agents must not be overly burdened with the collection and buffering of the information used to track resource timings that it affects web browsing.
Use-cases

A.                  A web developer collects latency information from a discrete set of resources to send back to their web servers.

B.                  Analytic scripts that lazy load at the end of a page load to collect latency information about resources loaded on the page.

Requirements

        i.            Retrieve timing from statically and dynamically declared resources;

      ii.            The ability for a web developer to collect all the resource timings on the page, or individually.

    iii.            Able to work on resources that do not have an onload event;

     iv.            Timing associated with the network;

       v.            Timings associated with loading the resource in the document, where applicable;

     vi.            A resource may be one of the following elements: frame/iframe, img, script, object, embed, css, css images, link, xhr, audio and video.

Best Regards,
Anderson Quach
IE Program Manager