I guess I can expand a bit more.. :) This is an exciting addition to the web platform, that will enable improved image compression at reduced CPU costs on the encoding side. Thanks for pushing this through!!
On Mon, Aug 24, 2026 at 2:15 PM Yoav Weiss (@Shopify) < [email protected]> wrote: > LGTM1 > > On Mon, Aug 24, 2026 at 1:08 PM Chromestatus < > [email protected]> wrote: > >> *Contact emails* >> [email protected], [email protected] >> >> *Explainer* >> *No information provided* >> >> *Specification* >> https://www.iso.org/standard/85066.html >> >> *Summary* >> Adds support for decoding JPEG XL (image/jxl) images in Blink using >> jxl-rs, a memory-safe pure Rust decoder (https://github.com/libjxl/jxl-rs). >> JPEG XL is a modern image format standardized as ISO/IEC 18181 that offers >> progressive decoding for improved perceived loading performance, support >> for wide color gamut, HDR, and high bit depth, and support for animation. >> >> *Blink component* >> Internals>Images>Codecs>JPEG XL >> <https://issues.chromium.org/issues?q=customfield1222907:%22Internals%3EImages%3ECodecs%3EJPEG%20XL%22> >> >> *Web Feature ID* >> jpegxl <https://webstatus.dev/features/jpegxl> >> >> *Motivation* >> (see Summary) >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> https://github.com/w3ctag/design-reviews/issues/633 >> >> *TAG review status* >> Issues addressed >> >> *Goals for experimentation* >> >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> No special risks. Note that the C++ and the Rust version are both tested >> against the same conformance test corpus. >> >> *Gecko*: Shipped/Shipping also migrating to rust version >> >> *WebKit*: Shipped/Shipping WebKit currently uses the C++ decoder. >> >> *Web developers*: Strongly positive >> >> *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? >> New feature, no special risk >> >> >> *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 >> https://wpt.fyi/results/jpegxl?label=experimental&label=master&aligned >> There is extensive conformance testing outside of WPT too. WPTs show >> failures because the flag is disabled in wpt runs. >> https://wpt.fyi/results/jpegxl?sha=3d06a34791fc33532baffe64e5c48c450cb1a1b9 >> shows a run with the flag enabled, which has two failures. The >> icc-uncommon-profile-reftest.html failure is a small difference visually, >> currently investigating. The cmyk-basic-conversion-reftest.html failure is >> being fixed in >> https://chromium-review.git.corp.google.com/c/chromium/src/+/8275513 >> >> *Flag name on about://flags* >> enable-jxl-image-format >> >> *Finch feature name* >> JXLImageFormat >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Availability expectation* >> Feature is available on Web Platform Baseline within 12 months of launch >> in Chrome. >> >> *Adoption expectation* >> Feature is considered a best practice for some use case within 12 months >> of reaching Web Platform baseline. >> >> *Adoption plan* >> Multiple players on the web have expressed interest in deploying JPEG XL >> images, including at least Cloudinary and Shopify, as well as multiple web >> developers during the Interop process. >> >> *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). >> N/A >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/5114042131808256?gate=6594362739916800 >> >> 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/6a8c2618.f0bac957.7b6f1.087d.GAE%40google.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a8c2618.f0bac957.7b6f1.087d.GAE%40google.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/CAOmohS%2B1zzOXQ9DPn0za1HyMGmqkrs0DO9EfiUM62oH8fG0w4w%40mail.gmail.com.
