Now that FETCH has the building blocks for measuring resource timings (see whatwg/fetch#1185 and w3c/resource-timing#252), the different resources have to integrate with it, so that the can decide exactly if and when to queue a resource timing entry.
The resources are:

Done:

• navigation: Integration with the HTML spec w3c/navigation-timing#141
• Beacon: Integrate with Resource Timing w3c/beacon#70
• Preload
• images & srcset/image-set: Report image loading to Resource Timing #7510
• scripts, workers & worklets: Report A and script loading to resource timing #7180
• Hyperlink audit (<a ping>): Report A and script loading to resource timing #7180
• SVG image: same as img, as decribed here.
• image button: Report ResourceTiming for video posters and image inputs #7539
• video poster: Report ResourceTiming for video posters and image inputs #7539
• link tag: Report link fetch resource timing #7559
• track: Report EventSource & track ResourceTiming entries #7553
• EventSource: Report EventSource & track ResourceTiming entries #7553
• embed & object: Report ResourceTiming for object and embed #7554
• iframes & frames: Report iframe & frame resource timing #7531
• media resource: Specify range fetching for media #7655

In Progress:

• prefetch: Specify processing model in terms of Fetch w3c/resource-hints#86

Resources that should avoid creating a resource timing entry:

• internal iframe navigation
• downloaded link
• WebSocket: not http(s), so doesn't get RT entries.