Can you tick the various review boxes (privacy, security, etc)? On Monday, September 21, 2026 at 8:17:27 PM UTC+2 [email protected] wrote:
> *> Specification* > *> https://github.com/whatwg/html/pull/11620 > <https://github.com/whatwg/html/pull/11620>* > > Is anything blocking this spec PR from landing? > > > *Interoperability and Compatibility* > *No information provided* > > Since this would change a shipped API, can you comment on the > compatibility risk? Is there a possibility that sites already using the > feature could be affected? > > -- Dan > > On Friday, September 18, 2026 at 3:04:11 AM UTC-7 [email protected] wrote: > >> *Contact emails* >> [email protected] >> > >> >> *Specification* >> https://github.com/whatwg/html/pull/11620 >> >> *Summary* >> When fetching rel=compression-dictionary links: >> > - Use "compression-dictionary" as request destination. >> - Properly set request's mode, credentials, referrer and referrerpolicy. >> - Take into account crossorigin and referrer attributes from <link >> rel="compression-dictionary">. >> >> *Blink component* >> Blink>Network >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ENetwork%22> >> >> *Web Feature ID* >> compression-dictionary-transport >> <https://webstatus.dev/features/compression-dictionary-transport> >> >> *Motivation* >> Compression Dictionary Transport was shipped in Chromium 130. Recently >> Mozilla and Igalia worked on some implementation in Firefox and WebKit, >> quite a bunch of tests have been added and the spec has been updated. This >> intent to ship is to catch up with the latest changes. >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Not applicable >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: Mozilla is implementing Compression dictionary transport and >> will have to align with the changes to make the test pass. >> >> *WebKit*: Igalia is currently upstreaming their implementation and we >> are aligned with these changes. >> >> *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 information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *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, see >> >> >> https://wpt.fyi/results/fetch/compression-dictionary/fetch-destination.tentative.https.html >> >> https://wpt.fyi/results/fetch/compression-dictionary/dictionary-fetch-with-link-element-crossorigin.tentative.https.html >> >> https://wpt.fyi/results/fetch/compression-dictionary/dictionary-fetch-with-link-referrer-and-referrerpolicy.tentative.https.html >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> CDTNewDestination, CDTNewCrossOriginHandling, >> CDTNewReferrerAndReferrerPolicyHandling >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://issues.chromium.org/issues/40255884 >> >> *Estimated milestones* >> Shipping on desktop 156 >> >> *Anticipated spec changes* >> The spec PRs are still being reviewed and firefox/webkit implementation >> is still in progress, so more changes may happen in the future. However, >> the three changes here seems uncontroversial they basically align >> rel=compression-dictionary links with what is done for other kind of links. >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/4895435813683200?gate=6090572807929856 >> >> 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/64e5b9d1-10f6-441d-a017-7921e36fc4aen%40chromium.org.
