- From: Skef Iterum <siterum@adobe.com>
- Date: Wed, 18 Sep 2024 21:39:14 +0000
- To: Garret Rieger <grieger@google.com>, "w3c-webfonts-wg (public-webfonts-wg@w3.org)" <public-webfonts-wg@w3.org>
- Message-ID: <CH3PR02MB913957926348BAEBFF2890BAB9622@CH3PR02MB9139.namprd02.prod.outlook.com>
Thanks for looking into this Garret! Looks like the meeting is Wednesday the 25 near lunch time, I'll be around and should be able to attend. Skef ________________________________ From: Garret Rieger <grieger@google.com> Sent: Wednesday, September 18, 2024 1:54 PM To: w3c-webfonts-wg (public-webfonts-wg@w3.org) <public-webfonts-wg@w3.org> Subject: Compression Streams API + Brotli EXTERNAL: Use caution when clicking on links or opening attachments. At previous calls we've discussed the Compression streams<https://github.com/whatwg/compression/blob/main/explainer.md> API which allows javascript to access compression and decompression libraries (like gzip) built into the browser. It currently doesn't support brotli. While this isn't specifically needed for IFT, a javascript implementation of IFT would greatly benefit from being able to use the native brotli decompression instead of providing its own. I checked in on the current state of adding brotli support to the api: * The feature request is being tracked here<https://github.com/whatwg/compression/issues/34> and it looks like adding support is being actively considered. * There will be a breakout session at TPAC this year to discuss adding support. Details here<https://github.com/w3c/tpac2024-breakouts/issues/72>, calendar event<https://www.w3.org/events/meetings/fccf73f3-01fc-424f-9106-a005bfc21ad5/>. I think it might be useful for some of the fonts wg (me and Skef?) to attend the breakout session and add support for supporting at least brotli decompression to the API.
Received on Wednesday, 18 September 2024 21:39:20 UTC