Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Intent to Prototype: contentEncoding in resource-timing
57 views
Skip to first unread message
Guohui Deng
Dec 17, 2024, 1:29:39 PM12/17/24
to blin...@chromium.org, nrose...@google.com
Contact emails
Explainer
Specification
PR to resource timing spec:
PR to fetch spec:
Summary
Add an explicit .contentEncoding value in resource-timing. More detailed discussion:
https://github.com/w3c/resource-timing/issues/381
Blink component
Motivation
New content encoding methods, like zstd and dictionary compression transports, are being experimented and deployed. Content will be delivered with a possibly large set of encoding choices even to the same client or from the same origin. Therefore, an explicit
.contentEncoding value in resource-timing would be clarifying to app developers.
Initial public proposal
None
Search tags
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
None
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?
None
Debuggability
None
Is this feature fully tested by
web-platform-tests?
No
Flag name on about://flags
None
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Tracking bug
Estimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages