Intent to Prototype: Content-type in Resource Timing

48 views

Skip to first unread message

Abin Paul

unread,

Oct 19, 2022, 11:01:17 AM10/19/22

to blin...@chromium.org

Summary

Adds the contentType field to PerformanceResourceTiming to hold a string corresponding to the content type of the fetched resource as returned by the server. The contentType field reflects the value returned by the server and not the sniffed value.

Blink component

Blink>PerformanceAPIs>ResourceTiming

Motivation

Servers and CDNs sometimes "swap out" file formats transparently (URL doesn't change) based on User Agent string, `Accept` headers or Client Hints when responding to a request for a resource. By providing access to the content type in those cases it would be possible for developers to know exactly which format the server has declared.

Initial public proposal

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

TAG review

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 behaviour of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

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

Yes

Flag name

ResourceTimingContentType

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1366706

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5156068351541248

This intent message was generated by Chrome Platform Status.

Reply all

Reply to author

Forward

0 new messages