Intent to Prototype: PerformanceResourceTiming.deliveryType

[Jeremy Roman]

Contact emails

jbr...@chromium.org

Explainer

https://github.com/w3c/resource-timing/issues/332

Specification

https://github.com/w3c/resource-timing/pull/343

(This is a pull request pending further discussion in the Web Perf WG and the authoring of suitable web platform tests.)

Summary

Expose information about how a resource was delivered. For example, resources which were delivered from the cache (currently exposed through transferSize) and navigations which were prefetched by the previous page are useful to identify.

Blink component

Blink>PerformanceAPIs>ResourceTiming

Motivation

This provides a way for navigational prefetch to be detected by authors, and additionally provides a more natural way to mark resources served from the HTTP cache. Potentially also useful for marking resources served from the preload (as in <link rel=preload>) cache.

Initial public proposal

https://github.com/w3c/resource-timing/issues/332

TAG review

none yet

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

Existing developer tools adequately cover the addition of a property.

Is this feature fully tested by web-platform-tests?

No, but WPT will be written alongside the implementation.

Flag name

Not landed yet, but likely "PerformanceResourceTimingDeliveryType".

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6347141115543552

This intent message was generated by Chrome Platform Status.