LGTM1 Thank you for working on this important addition that would enable easier deployment of new content encodings.
On Fri, Sep 26, 2025 at 11:11 AM 'Guohui Deng' via blink-dev < [email protected]> wrote: > *Contact emails* > [email protected] > > *Explainer* > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ResourceTimingContentEncoding/Content_Encoding.md > > *Specification* > Https://fetch.spec.whatwg.org/#request-body-header-name > <https://fetch.spec.whatwg.org/#request-body-header-name> > > https://www.w3.org/TR/resource-timing/#dom-performanceresourcetiming-contentencoding > > > *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). > More detailed discussion: > https://github.com/w3c/resource-timing/issues/381 > > *Blink component* > Blink>PerformanceAPIs>ResourceTiming > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPerformanceAPIs%3EResourceTiming%22> > > *Web Feature ID* > resource-timing <https://webstatus.dev/features/resource-timing> > > *Search tags* > contentEncoding <https://chromestatus.com/features#tags:contentEncoding>, > resource-timing <https://chromestatus.com/features#tags:resource-timing> > > *TAG review* > https://github.com/w3ctag/design-reviews/issues/1064 > > *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 > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>* > *?* > Yes: > https://wpt.fyi/results/resource-timing/content-encoding.https.html?label=experimental&label=master&aligned > > *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* > https://issuetracker.google.com/issues/327941462 > > *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* > https://chromestatus.com/feature/4818080273006592?gate=5147198382407680 > > *Links to previous Intent discussions* > Intent to Prototype: > > https://groups.google.com/a/chromium.org/g/blink-dev/c/fTt7dGZcQ80/m/9z9amofjBAAJ > > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > 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 [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN6PR00MB2371A82A3495A094F8DEC073C01EA%40MN6PR00MB2371.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN6PR00MB2371A82A3495A094F8DEC073C01EA%40MN6PR00MB2371.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSKMYRmL4Zy%2BVKnVqN1TMjeJ0YjfY-mbZqkTJ1r6GUWm%3DQ%40mail.gmail.com.
