Intent to Ship: contentEncoding in resource-timing

14 views
Skip to first unread message

Guohui Deng

unread,
Sep 26, 2025, 5:11:30 AM (yesterday) Sep 26
to Abridged recipients
Contact emails
Explainer
Specification


Summary

This provides access to Content-Encoding values in ResourceTiming to enable developers to effectively experiment with new content encodings, monitor performance, and debug issues using Real User Monitoring (RUM).
Blink component
Web Feature ID
Search tags
TAG review
TAG review status
Resolution: satisfied

Risks
N/A

Interoperability and Compatibility
None

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1189)

WebKit: Support (https://github.com/WebKit/standards-positions/issues/467)

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?

No, this feature only adds a new property in resource timing.


Debuggability
None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by web-platform-tests?
Flag name on about://flags
None

Finch feature name
ResourceTimingContentEncoding

Non-finch justification
None

Rollout plan
Will ship enabled for all users

Requires code in //chrome?
False

Tracking bug
Availability expectation
Availability in other browsers are not expected soon, although webkit signaled support for this feature.

Adoption expectation
It's expected that some sites who uses complicated content encoding schemes would like to use this feature for optimization.

Non-OSS dependencies
Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function? 
No.

Estimated milestones
No milestones specified


Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). 

Spec changes have already been merged to both "fetch" and "resource timing".  Links to the spec are listed above in this document.

Link to entry on the Chrome Platform Status
Links to previous Intent discussions
Intent to Prototype:
 


This intent message was generated by Chrome Platform Status.

Yoav Weiss (@Shopify)

unread,
Sep 26, 2025, 5:19:02 AM (yesterday) Sep 26
to Guohui Deng, Abridged recipients
LGTM1

Thank you for working on this important addition that would enable easier deployment of new content encodings.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN6PR00MB2371A82A3495A094F8DEC073C01EA%40MN6PR00MB2371.namprd00.prod.outlook.com.

Mike Taylor

unread,
Sep 26, 2025, 9:11:51 AM (23 hours ago) Sep 26
to Yoav Weiss (@Shopify), Guohui Deng, Abridged recipients

Could you please request reviews for security, privacy, enterprise etc in your chromestatus entry?

Reply all
Reply to author
Forward
0 new messages